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.

Sign up for GitHub

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

CBMC version 6 release process changes #7987

Merged
merged 5 commits into from
Nov 13, 2023
+82 −64
Merged

CBMC version 6 release process changes #7987

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5b1c0ff
Mark new releases as prerelease
NlightNFotis Oct 30, 2023
2d14e99
Temporarily deactivate homebrew PR and docker image push.
NlightNFotis Oct 30, 2023
b2925f3
Mark version 6.0.0 preview of CBMC
NlightNFotis Oct 30, 2023
821d58c
Change version string handling to ignore suffixes in CMakeLists.txt
NlightNFotis Nov 1, 2023
b580d85
Add scratch file for a v6 release process undo stack
NlightNFotis Nov 1, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions v6_undo_stack.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Temporary changes for v6

This is a temporary file, containing changes done to release process for v6,
that need to be reverted back.

It's a file in the repository to allow for easier tracking of the status
of things among the broader community, and to allow everyone to add/delete
things they believe should be in here.

The file is scheduled for deletion by the actual release of `v6` and subsequent
rollback of the changes.

## Stack

* Revert changes to homebrew PR push (`.github/workflows/release-packages.yaml`)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit hashes could be really handy here, assuming that we can avoid invalidating them in a re-base before the PR is merged.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if we need commit hashes here - this was supposed to be a casual thing just to verify our reverted changes against the log here, sort of a double-entry bookkeeping practice but for the purpose of managing the process.

But if keen, I can also add this in a new PR.

* Revert changes to docker image push (`.github/workflows/releas-packages.yaml`)
* Remove marking of release as `prerelease` (`.github/workflows/regular-release.yaml`)
Loading