Skip to content

v0.5.0

Latest
Latest
Compare
Choose a tag to compare
@jfreda jfreda released this 14 Feb 23:23
v0.5.0
caa1b99
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Configuration changes

  • Enabling Google Group approvers:
google_workspace {
  ...
  // group_approvals is the configuration for using Google Groups as document
  // approvers.
  group_approvals {
    // enabled enables using Google Groups as document approvers.
    enabled = true

    // search_prefix is the prefix to use when searching for Google Groups.
    search_prefix = "team-"
  }
  ...
}

Notable features & enhancements

  • (NEW) Support for Google Group approvers: Google Groups will be listed as approvers first in the document header, followed by individual approvers. When a member of a Google Group approver approves the document, they will be added as an individual approver.
  • Projects: Projects are now fully enabled (feature flag was removed). Project resources can now be reordered via drag-and-drop. Pagination was added to the projects route.
  • Document approvers can remove themselves as an approver.
  • Document/draft owners can now transfer ownership to another user. This will share the Google Doc with the new owner with "edit" permissions, and send an email notification to the new owner.
  • Emails now look nice (previously were just plaintext).
  • Document status can now be changed via a dropdown in the sidebar (previously was a "Move to STATUS" button).
  • Recently-viewed projects are tracked and shown along with recently-viewed documents.
  • An email will be sent to the document owner after each approver approves the document.
  • The document owner filter (under "All Docs") is now searchable.
  • The document created date is reset when a document is published (previously was the date the draft was created).
  • Document approvers now get "Edit" access in Google Docs.
  • Performance improvements: get all projects; get a document; get a project's related resources

Security updates

  • If using Okta+AWS ALB for auth, the signer field in the JWT header from the AWS ALB is now validated. The trusted signer is now required, and can be set in the Hermes config file or a HERMES_SERVER_OKTA_JWT_SIGNER environment variable.

What's Changed

Full Changelog: v0.4.0...v0.5.0

Contributors

jeffdaley and jfreda
Assets 2
Loading