Skip to content

Release v1.0.1 #263

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
9 of 16 tasks
elezar opened this issue Mar 19, 2025 · 1 comment
Closed
9 of 16 tasks

Release v1.0.1 #263

elezar opened this issue Mar 19, 2025 · 1 comment
Milestone

Comments

@elezar
Copy link
Contributor

elezar commented Mar 19, 2025

The v1.0.1 release is a dependency-update release. The v1.0.0 release depends on gopkg.in/yaml.v2 v2.4.0 and this is passed on to consumers such as containerd and buildkit as a transitive dependency. Since these dependencies have since moved to gopkg.in/yaml.v3 making the switch here will greatly reduce the amount of vendored code that they have to pull in JUST for CDI.

Note that the gopkg.in/yaml.v2 is only explicitly used when producing ordered CDI specifications and the sigs.k8s.io/yaml package is used in all other case.

There are no CDI Specification changes in this release.

Release Process

  • Create a PR titled Bump version to v1.0.1 including the following changes Bump version to v1.0.1 #265:
    • Change the following to the target version v1.0.1:
      • the CurrentVersion in specs-go/versions.go,
      • the tags.cncf.io/container-device-interface version in schema/go.mod,
      • (for specification changes only) the tags.cncf.io/container-device-interface/specs-go version in go.mod,
      • (for specification changes only) the tags.cncf.io/container-device-interface/specs-go version in schema/go.mod.
    • Run make mod-tidy to update versions in cmd/**/go.mod.
    • Run make mod-verify to ensure modules are up to date.
    • (for specification changes only) Add a description to the specification changes in SPEC.md.
    • (for specification changes only) Implement a requiresV* function for the target version in specs-go/versions.go.
  • Merge the PR on sufficient approval.
  • Create a v1.0.1 tag.
  • (for specification changes only) Create a specs-go/vX.Y.W tag. (for the first spec version W will be the same as Z)
  • Create a GitHub release form the v1.0.1 tag.
  • (for specification changes only) Create a GitHub release from the specs-go/vX.Y.Z tag.
  • Close the release issue.
@elezar elezar added this to the v1.0.1 milestone Mar 19, 2025
@elezar
Copy link
Contributor Author

elezar commented Mar 22, 2025

@elezar elezar closed this as completed Mar 22, 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

No branches or pull requests

1 participant