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

Update chronicle to v0.8.0 #2154

Merged
merged 1 commit into from
Sep 20, 2023
Merged

Update chronicle to v0.8.0 #2154

merged 1 commit into from
Sep 20, 2023

Conversation

wagoodman
Copy link
Contributor

This PR adjusts the release pipeline to use annotated tags over lightweight tags and updates chronicle to the latest version to leverage this.

While looking at the old release logs I noticed that the cache keys are not unique, thus are causing cache restore errors (which file silently). Additionally I also removed an unused env var.

@wagoodman wagoodman marked this pull request as ready for review September 20, 2023 13:50
@wagoodman wagoodman requested a review from a team September 20, 2023 13:50
@@ -123,7 +120,9 @@ jobs:

- name: Tag release
run: |
git tag ${{ github.event.inputs.version }}
git config --global user.name "anchoreci"
Copy link
Contributor

Choose a reason for hiding this comment

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

Why pass --global? Is this setting correct for every job that runs on this CI worker? (Maybe it is, come to think of it.)

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 can leave off global and it would also still function (I added it out of habit), but leaving the global flag will not affect other jobs as the github hosted CI runners don't allow for persisted state (you get a clean state every time).

@wagoodman wagoodman merged commit 40899ad into main Sep 20, 2023
@wagoodman wagoodman deleted the use-annotated-tags branch September 20, 2023 14:11
GijsCalis pushed a commit to GijsCalis/syft that referenced this pull request Feb 19, 2024
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