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

Prep for release v3.9.39 #1480

Merged
merged 5 commits into from
Nov 14, 2024
Merged

Prep for release v3.9.39 #1480

merged 5 commits into from
Nov 14, 2024

Conversation

spatten
Copy link
Contributor

@spatten spatten commented Nov 13, 2024

Overview

Prep for a release to pull in some licensing changes in Themis.

https://github.com/fossas/themis/pull/81
https://github.com/fossas/themis/pull/79

I also made a minor edit to the release documentation so that I don't have to type the tag name multiple times when cutting a release.

Acceptance criteria

  • The changelog is fine
  • We like the new release instructions
  • We pull in the new version of Themis

Testing plan

This is a doc-only change, and the licensing changes are tested in Themis, so no testing is required.

Risks

None

Metrics

Nope

References

Checklist

  • I added tests for this PR's change (or explained in the PR description why tests don't make sense).
  • If this PR introduced a user-visible change, I added documentation into docs/.
  • If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
  • If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an ## Unreleased section at the top.
  • If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
  • If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.

@spatten spatten marked this pull request as ready for review November 13, 2024 22:13
@spatten spatten requested a review from a team as a code owner November 13, 2024 22:13
@spatten spatten requested a review from jssblck November 13, 2024 22:13
Changelog.md Outdated Show resolved Hide resolved
Co-authored-by: Jessica Black <me@jessica.black>
@spatten spatten enabled auto-merge (squash) November 13, 2024 22:16
@spatten spatten merged commit 4471697 into master Nov 14, 2024
17 of 18 checks passed
@spatten spatten deleted the prep-for-release-v3.9.39 branch November 14, 2024 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants