Release container-device-interface v1.0.0

[bart0sh]

• Create a PR titled Bump version to v1.0.0 including the following changes:
  • Change the following to the target version v1.0.0:
    • 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.0 tag.
• (for specification changes only) Create a specs-go/v1.0.0 tag. (for the first spec version w will be the same as z)
• Create a GitHub release form the v1.0.0 tag.
• (for specification changes only) Create a GitHub release from the specs-go/v1.0.0 tag.
• Close the release issue.

[elezar]

Thanks @bart0sh.

How do we feel about a script (e.g. /hack/prepare-release.sh) that uses the gh CLI to create this issue for a given version?

[klihub]

Thanks @bart0sh.

How do we feel about a script (e.g. /hack/prepare-release.sh) that uses the gh CLI to create this issue for a given version?

@elezar We could also set up an issue template for new releases, like this: #261