adding pagination to get more buried releases, removes testing for prereleases #69
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for noir-vite-hardhat ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@noir-lang/[email protected], npm/@noir-lang/[email protected], npm/@noir-lang/[email protected], npm/@noir-lang/[email protected], npm/@noir-lang/[email protected] |
catmcgee
approved these changes
Jan 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added some pagination
CI was failing because it didn't get any releases, and the reason for that is that there are SO MANY
aztecsthat it can't really find anything.This should get us 300 releases. This should get us pretty much every release in existence.
Removed the prereleases
Left a comment in the code, as the code could look a little bit over-engineered and I don't want that reputation 😄
(I'm joking, but yeah I found out we don't have a stable release cycle, for example at this point in time, stable is 0.22.0 and prerelease is... 0.21.0... so it would be a totally useless and misleading test)
Updated to 0.22.0
Seems like it will break with 0.23.0 though