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.8.1 #2407

Merged
merged 16 commits into from
Sep 3, 2024
Merged

Release v7.8.1 #2407

merged 16 commits into from
Sep 3, 2024

Conversation

asjohnston-asf
Copy link
Member

Verification job ran successfully: https://hyp3-test-api.asf.alaska.edu/jobs/69c58c60-f4e5-41f8-b7fb-1950f72a8ba1

Vertex test is still able to interact with the API, so CORS is still working as expected.

dependabot bot and others added 16 commits September 2, 2024 19:46
Bumps [openapi-core](https://github.com/python-openapi/openapi-core) from 0.19.3 to 0.19.4.
- [Release notes](https://github.com/python-openapi/openapi-core/releases)
- [Commits](python-openapi/openapi-core@0.19.3...0.19.4)

---
updated-dependencies:
- dependency-name: openapi-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [boto3](https://github.com/boto/boto3) from 1.35.6 to 1.35.10.
- [Release notes](https://github.com/boto/boto3/releases)
- [Commits](boto/boto3@1.35.6...1.35.10)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [flask-cors](https://github.com/corydolphin/flask-cors) from 4.0.1 to 5.0.0.
- [Release notes](https://github.com/corydolphin/flask-cors/releases)
- [Changelog](https://github.com/corydolphin/flask-cors/blob/main/CHANGELOG.md)
- [Commits](corydolphin/flask-cors@4.0.1...5.0.0)

---
updated-dependencies:
- dependency-name: flask-cors
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [setuptools](https://github.com/pypa/setuptools) from 73.0.1 to 74.1.0.
- [Release notes](https://github.com/pypa/setuptools/releases)
- [Changelog](https://github.com/pypa/setuptools/blob/main/NEWS.rst)
- [Commits](pypa/setuptools@v73.0.1...v74.1.0)

---
updated-dependencies:
- dependency-name: setuptools
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [cfn-lint](https://github.com/aws-cloudformation/cfn-lint) from 1.10.3 to 1.11.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.10.3...v1.11.1)

---
updated-dependencies:
- dependency-name: cfn-lint
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@asjohnston-asf asjohnston-asf added the patch Bump the patch version number of this project label Sep 3, 2024
@asjohnston-asf asjohnston-asf requested a review from a team as a code owner September 3, 2024 17:16
Copy link

github-actions bot commented Sep 3, 2024

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 35eb668 into main Sep 3, 2024
22 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.

2 participants