Skip to content

Bump version to v1.0.0 #260

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

Merged
merged 1 commit into from
Mar 7, 2025

Conversation

bart0sh
Copy link
Contributor

@bart0sh bart0sh commented Mar 7, 2025

Ref: #259

@bart0sh bart0sh requested review from elezar and klihub March 7, 2025 11:07
@bart0sh bart0sh force-pushed the PR026-Bump-version-to-v1.0.0 branch from 94060c0 to 9dc896d Compare March 7, 2025 11:08
@@ -9,7 +9,7 @@ require (
github.com/spf13/cobra v1.6.0
gopkg.in/yaml.v2 v2.4.0
sigs.k8s.io/yaml v1.3.0
tags.cncf.io/container-device-interface v0.0.0
tags.cncf.io/container-device-interface v1.0.0
Copy link
Contributor

Choose a reason for hiding this comment

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

More a comment on the release process: These are probably not strictly necessary since these CLIs are not generally consumed externally, but it's probably more consistent to have them.

Copy link
Contributor

@klihub klihub Mar 7, 2025

Choose a reason for hiding this comment

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

I was wondering the same. We anyway have the replace rule, so the version here has no effect, but if we bump it now, we should always go through the motions for consistency. @bart0sh So wouldn't leaving this at 0.0.0 be easier and less of a burden for maintenance ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done.

@@ -9,7 +9,7 @@ require (
github.com/spf13/cobra v1.6.0
gopkg.in/yaml.v2 v2.4.0
sigs.k8s.io/yaml v1.3.0
tags.cncf.io/container-device-interface v0.0.0
tags.cncf.io/container-device-interface v1.0.0
tags.cncf.io/container-device-interface/schema v0.0.0
Copy link
Contributor

Choose a reason for hiding this comment

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

Question: Do we want to also specify a version for this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

reverted

Copy link
Contributor Author

Choose a reason for hiding this comment

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

brougth both changes back as reverting them resulted in CI failures: https://github.com/cncf-tags/container-device-interface/actions/runs/13724737021

Copy link
Contributor

@elezar elezar left a comment

Choose a reason for hiding this comment

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

Minor comments -- more related to the release process and not blockers.

Copy link
Contributor

@klihub klihub left a comment

Choose a reason for hiding this comment

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

I'm also fine with this, although I think it would be less of a maintenance burden to keep the in repo replaced version references always at v0.0.0 and never touch them. Otherwise, we always need to remember to bump them for consistency, even if this has absolutely no effect.

@bart0sh bart0sh force-pushed the PR026-Bump-version-to-v1.0.0 branch from 9dc896d to df41b6a Compare March 7, 2025 16:16
@bart0sh
Copy link
Contributor Author

bart0sh commented Mar 7, 2025

I've just realised that those changes were made by make mod-tidy && make mod-verify. Should I commit them again?

Signed-off-by: Ed Bartosh <[email protected]>
@bart0sh bart0sh force-pushed the PR026-Bump-version-to-v1.0.0 branch from df41b6a to 6784e01 Compare March 7, 2025 16:20
@bart0sh
Copy link
Contributor Author

bart0sh commented Mar 7, 2025

Without them CI jobs failed.

@klihub klihub merged commit 40e4c31 into cncf-tags:main Mar 7, 2025
8 checks passed
@klihub
Copy link
Contributor

klihub commented Mar 7, 2025

Merged.

@klihub
Copy link
Contributor

klihub commented Mar 7, 2025

Without them CI jobs failed.

Ah, ok. Fair enough.

@elezar
Copy link
Contributor

elezar commented Mar 8, 2025

I've just realised that those changes were made by make mod-tidy && make mod-verify. Should I commit them again?

I think if the changes are made by tooling then that's fine. I don't want us to have to manually update things in those modules.

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