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

Use 16-draft as the version identifier of the next version #122

Merged
merged 1 commit into from
Dec 31, 2024

Conversation

rnestler
Copy link
Member

This allows to test the validator, while making sure that we do not have an outdated version of the spec in the validator library once the next version gets released.

This allows to test the validator, while making sure that we do not have
an outdated version of the spec in the validator library once the next
version gets released.
@rnestler rnestler requested a review from a team December 31, 2024 00:24
@dbrgn
Copy link
Contributor

dbrgn commented Dec 31, 2024

👌🏻

we don't have a release checklist, right? reverting this would need to be on it.

@rnestler
Copy link
Member Author

rnestler commented Dec 31, 2024

we don't have a release checklist, right? reverting this would need to be on it.

We should create one. See #123

@rnestler rnestler merged commit cc27cd4 into master Dec 31, 2024
10 checks passed
@rnestler rnestler deleted the use-16-draft-as-version-identifier branch December 31, 2024 16:43
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