Skip to content

Conversation

@asjohnston-asf
Copy link
Member

Golden INSAR_ISCE_BURST test still passes after delivery to test: https://github.com/ASFHyP3/hyp3-testing/actions/runs/18606318834

I confirmed the test environment is pulling ghcr.io/asfhyp3/hyp3-isce2:3.0.1 as expected, while prod is still pulling ghcr.io/asfhyp3/hyp3-isce2:latest as expected.

dependabot bot and others added 5 commits October 13, 2025 19:08
Bumps the pip-deps group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [boto3](https://github.com/boto/boto3) | `1.40.45` | `1.40.50` |
| [asf-enumeration](https://github.com/ASFHyP3/asf-enumeration) | `0.3.0` | `0.4.0` |
| [ruff](https://github.com/astral-sh/ruff) | `0.13.3` | `0.14.0` |
| [setuptools-scm](https://github.com/pypa/setuptools-scm) | `9.2.0` | `9.2.1` |
| [cfn-lint](https://github.com/aws-cloudformation/cfn-lint) | `1.40.0` | `1.40.1` |


Updates `boto3` from 1.40.45 to 1.40.50
- [Release notes](https://github.com/boto/boto3/releases)
- [Commits](boto/boto3@1.40.45...1.40.50)

Updates `asf-enumeration` from 0.3.0 to 0.4.0
- [Release notes](https://github.com/ASFHyP3/asf-enumeration/releases)
- [Changelog](https://github.com/ASFHyP3/asf-enumeration/blob/develop/CHANGELOG.md)
- [Commits](ASFHyP3/asf-enumeration@v0.3.0...v0.4.0)

Updates `ruff` from 0.13.3 to 0.14.0
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@0.13.3...0.14.0)

Updates `setuptools-scm` from 9.2.0 to 9.2.1
- [Release notes](https://github.com/pypa/setuptools-scm/releases)
- [Changelog](https://github.com/pypa/setuptools-scm/blob/main/CHANGELOG.md)
- [Commits](pypa/setuptools-scm@v9.2.0...v9.2.1)

Updates `cfn-lint` from 1.40.0 to 1.40.1
- [Release notes](https://github.com/aws-cloudformation/cfn-lint/releases)
- [Changelog](https://github.com/aws-cloudformation/cfn-lint/blob/main/CHANGELOG.md)
- [Commits](aws-cloudformation/cfn-lint@v1.40.0...v1.40.1)

---
updated-dependencies:
- dependency-name: boto3
  dependency-version: 1.40.50
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: pip-deps
- dependency-name: asf-enumeration
  dependency-version: 0.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: pip-deps
- dependency-name: ruff
  dependency-version: 0.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: pip-deps
- dependency-name: setuptools-scm
  dependency-version: 9.2.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: pip-deps
- dependency-name: cfn-lint
  dependency-version: 1.40.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: pip-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
pin INSAR_ISCE_BURST to last hyp3-isce2 release
@asjohnston-asf asjohnston-asf requested review from a team as code owners October 17, 2025 23:12
@asjohnston-asf asjohnston-asf added the patch Bump the patch version number of this project label Oct 17, 2025
@github-actions
Copy link

github-actions bot commented Oct 17, 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?

@asjohnston-asf asjohnston-asf merged commit d0afc68 into main Oct 20, 2025
27 checks passed
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.

3 participants