Skip to content

Release v10.0.0#2662

Merged
williamh890 merged 84 commits intomainfrom
develop
Mar 11, 2025
Merged

Release v10.0.0#2662
williamh890 merged 84 commits intomainfrom
develop

Conversation

@williamh890
Copy link
Copy Markdown
Contributor

No description provided.

williamh890 and others added 30 commits February 28, 2025 13:02
Co-authored-by: Jake Herrmann <jtherrmann@alaska.edu>
Co-authored-by: Jake Herrmann <jtherrmann@alaska.edu>
@williamh890 williamh890 added the major Bump the major version number of this project label Mar 11, 2025
@williamh890 williamh890 requested review from a team as code owners March 11, 2025 19:24
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 11, 2025

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 jtherrmann temporarily deployed to hyp3-opera-disp-sandbox March 11, 2025 19:25 — with GitHub Actions Inactive
@jtherrmann jtherrmann temporarily deployed to hyp3-a19-jpl-test March 11, 2025 19:25 — with GitHub Actions Inactive
@jtherrmann jtherrmann temporarily deployed to hyp3-tibet-jpl-test March 11, 2025 19:25 — with GitHub Actions Inactive
@jtherrmann jtherrmann temporarily deployed to hyp3-its-live-test March 11, 2025 19:25 — with GitHub Actions Inactive
@jtherrmann
Copy link
Copy Markdown
Contributor

jtherrmann commented Mar 11, 2025

Confirmed that /costs response schema renders correctly at https://hyp3-test-api.asf.alaska.edu, actual /costs response matches https://hyp3-docs.asf.alaska.edu/using/credits/, and submitting some random jobs decrements my user credits by the correct amount.

Edit: Additionally, @williamh890 validated changes in a sandbox deployment, see #2637 (comment) and #2637 (comment) and also confirmed that Vertex works with both the sandbox deployment and hyp3-test

@williamh890 williamh890 merged commit e257c10 into main Mar 11, 2025
@jtherrmann
Copy link
Copy Markdown
Contributor

Performed similar validation for edc-prod.

Sample jobs: https://hyp3-api.asf.alaska.edu/jobs?user_id=jtherrmann&name=20250311

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

major Bump the major version number of this project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants