Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v7.2.2 #2280

Closed
wants to merge 2 commits into from
Closed

Release v7.2.2 #2280

wants to merge 2 commits into from

Conversation

jtherrmann
Copy link
Contributor

@jtherrmann jtherrmann commented May 13, 2024

Validate for https://hyp3-enterprise-test.asf.alaska.edu/:

  • Favicon renders
  • 200 response is good for all endpoints
  • 400 response is good for all endpoints that have one

Validate for https://hyp3-test-api.asf.alaska.edu/:

  • Favicon renders
  • 200 response is good for all endpoints
  • 400 response is good for all endpoints that have one

@jtherrmann jtherrmann added the patch Bump the patch version number of this project label May 13, 2024
Copy link

Developer checklist

  • Indicated the level of changes to this package by affixing one of these labels:
    • major -- Major changes to the API that may break current workflows
    • minor -- Minor changes to the API that do not break current workflows
    • patch -- Patches and bugfixes for the current version that do not break current workflows
    • bumpless -- Changes to documentation, CI/CD pipelines, etc. that don't affect the software's version
  • (If applicable) Updated the dependencies and indicated any downstream changes that are required
  • Added/updated documentation for these changes
  • Added/updated tests for these changes
  • Verified changes in test deployment and summarized results, e.g. in PR description or comments on the related issue(s)
  • If the step function code has changed, have you drained the job queue before merging?
    • For example, if the interface for a Lambda function has changed to expect different input,
      then currently running jobs (which use the old step function definition) will call the new
      function with the old input. So we must drain the job queue before deployment, so that the new
      function is only called by the new step function definition.

Reviewer checklist

  • Have all dependencies been updated?
  • Is the level of changes labeled appropriately?
  • Are all the changes described appropriately in CHANGELOG.md?
  • Has the documentation been adequately updated?
  • Are the tests adequate?
  • Have the changes been verified in the test deployment?

@jtherrmann
Copy link
Contributor Author

Now that #2268 is closed, serving images becomes much less important, so I'm closing this PR.

@jtherrmann jtherrmann closed this May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Bump the patch version number of this project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant