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

question: did you move the 0.26.0 tag? #1145

Closed
colemickens opened this issue Apr 5, 2024 · 1 comment
Closed

question: did you move the 0.26.0 tag? #1145

colemickens opened this issue Apr 5, 2024 · 1 comment
Assignees
Labels
bug needs triage Waiting for discussion / prioritization by team

Comments

@colemickens
Copy link

Steps to Reproduce

Did you move the 0.26.0 tag after publishing?

  1. I noticed that we had a hash mismatch for 0.26.0 sources.
  2. While looking into it, I noticed that one of the nixpkgs automation accounts sent two different PRs for the same pacakge bump, indeed both with different hashes.

In light of recent events, I'd like to understand how this is possible and happened. And, if you did move the tag, I'd ask you that you consider not doing this in the future.

Your Environment

n/a

Expected Behavior

n/a

Actual Behavior

n/a

Additional Context

n/a

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@colemickens colemickens added bug needs triage Waiting for discussion / prioritization by team labels Apr 5, 2024
@hslatman hslatman self-assigned this Apr 9, 2024
@hslatman
Copy link
Member

Hi @colemickens, no, as far as we know, we did not move the tag. Feel free to reopen if it reoccurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

2 participants