Skip to content

Bump spec version to v0.9.0 #252

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

Closed
wants to merge 1 commit into from
Closed

Conversation

elezar
Copy link
Contributor

@elezar elezar commented Feb 17, 2025

No description provided.

Comment on lines +143 to +149
// requiresV090 returns true if the spec uses v0.9.0 features.
// Since the v0.9.0 spec bump was due to moving the minimum version checks to
// the spec package, there are no explicit spec changes.
func requiresV090(_ *Spec) bool {
return false
}

Copy link
Contributor

@klihub klihub Feb 24, 2025

Choose a reason for hiding this comment

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

This is just out of curiosity: is there any difference between validSpecVersions[$VERSION] being nil and it being a (requiredFunc) function which always returns false ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There is no difference functionally. We could remove the requiresV080 and requiresV090 functions entirely.

Copy link
Contributor

@klihub klihub Feb 26, 2025

Choose a reason for hiding this comment

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

Ok. Just wanted to make sure I understand it correctly. From my perspective, there is no need to remove those functions to get this merged. There is one benefit to having those functions there as opposed to omitting them: it spells out that this bit of functionality has been considered/taken care of, but it just happens that there are no new additions to the Spec in those versions.

@bart0sh
Copy link
Contributor

bart0sh commented Feb 28, 2025

@elezar I'd propose to close this PR in favour of #257 as we agreed to release current main branch as 1.0.0 recently.

@bart0sh
Copy link
Contributor

bart0sh commented Mar 7, 2025

Closing as #257 is merged.

@bart0sh bart0sh closed this Mar 7, 2025
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.

3 participants