Skip to content

Latest commit

 

History

History
15 lines (12 loc) · 1.99 KB

RELEASING.md

File metadata and controls

15 lines (12 loc) · 1.99 KB

Releasing

Deploying titiler-multidim to VEDA environments is configured and executed via the veda-deploy repo.

Release Workflow:

  1. Open pull requests: PRs are made to the main branch. PRs should include tests and documentation. pytest should succeed before merging. If appropriate, changes should be added to the CHANGELOG.md file under the Unreleased header.
  2. Deploy to SMCE Staging: Once merged, deploy titiler-multidim to the smce-staging environment of veda-deploy.
    1. Verify TITILER_MULTIDIM_GIT_REF in the smce-staging environment of veda-deploy is set to main.
    2. Follow the steps in veda-deploy's How to deploy section. Select smce-staging for Environment to deploy to and ensure only DEPLOY_TITILER_MULTIDIM is checked.
  3. Deploy to MCP Prod: When it is time to release changes to veda-deploy's MCP environment:
    1. Add a new release version heading (e.g. v0.2.1) to the top of CHANGELOG.md under the Unreleased header, so previously unreleased changes are documented as a part of the new release and new changes can still be added under Unreleased.
    2. Tag main with the new release version (e.g. v0.2.1).
    3. Update the TITILER_MULTIDIM_GIT_REF in veda-deploy's MCP environment to the release tag (e.g. v0.2.1).
    4. Follow the steps in veda-deploy's How to deploy section. Select mcp-prod for Environment to deploy to and ensure only DEPLOY_TITILER_MULTIDIM is checked.