Skip to content

Release for v0.7.0#3440

Open
github-actions[bot] wants to merge 2 commits into
mainfrom
tagpr-from-v0.6.0
Open

Release for v0.7.0#3440
github-actions[bot] wants to merge 2 commits into
mainfrom
tagpr-from-v0.6.0

Conversation

@github-actions

@github-actions github-actions Bot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

This pull request is for the next release as v0.7.0 created by tagpr. Merging it will tag v0.7.0 to the merge commit and create a GitHub release.

You can modify this branch "tagpr-from-v0.6.0" directly before merging if you want to change the next version number or other files for the release.

How to change the next version as you like

There are two ways to do it.

  • Version file
    • Edit and commit the version file specified in the .tagpr configuration file to describe the next version
    • If you want to use another version file, edit the configuration file.
  • Labels convention
    • Add labels to this pull request like "tagpr:minor" or "tagpr:major"
    • If no conventional labels are added, the patch version is incremented as is.

What's Changed

💪 Improvements

🐛 Bug Fixes

📖 Documentation improvements

🧪 Test improvements and Misc Fixes

Other Changes

New Contributors

Full Changelog: v0.6.0...tagpr-from-v0.6.0

@github-actions github-actions Bot added the tagpr label Mar 2, 2026
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch 7 times, most recently from dd3c4a8 to bd08e83 Compare March 8, 2026 23:23
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch 3 times, most recently from 7aa0352 to 0163553 Compare March 17, 2026 04:41
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch 3 times, most recently from e3e906d to ba5d48a Compare March 23, 2026 12:24
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch 8 times, most recently from f7795d6 to 8d50d89 Compare April 4, 2026 07:37
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch 7 times, most recently from 3a37c25 to ab222f1 Compare April 13, 2026 14:50
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch from ab222f1 to 9bc37d7 Compare April 15, 2026 12:36
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch from ff79d6f to bc57ab4 Compare May 9, 2026 04:02
@utam0k

utam0k commented May 9, 2026

Copy link
Copy Markdown
Member

@youki-dev/youki I've just set up the v0.6.1 milestone. Please add any PRs or issues you want to see in the next release.
https://github.com/youki-dev/youki/milestone/4

@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch 9 times, most recently from 1fe3fb2 to bd9502c Compare May 22, 2026 10:13
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch 7 times, most recently from 8c400a2 to 902b611 Compare May 30, 2026 22:57
@github-actions
github-actions Bot force-pushed the tagpr-from-v0.6.0 branch 4 times, most recently from fb0be8d to 994a9d4 Compare June 11, 2026 12:17
@nayuta723

Copy link
Copy Markdown
Contributor

@utam0k
As we move forward with the release, I’m considering releasing this as v0.7.0 since it includes breaking changes from oci-spec as well.

Would it make sense to include time namespace support before proceeding with the release?

@utam0k

utam0k commented Jul 16, 2026

Copy link
Copy Markdown
Member

@utam0k As we move forward with the release, I’m considering releasing this as v0.7.0 since it includes breaking changes from oci-spec as well.

Would it make sense to include time namespace support before proceeding with the release?

+1

@JosiahParry

Copy link
Copy Markdown
Contributor

Chiming in as a downstream user of libcontainer and oci_spec:

If breaking changes are included, i would personally prefer if those came with a major version bump to match with semver. We use renovate to automatically suggest version changes. We merge changes without much checking if they are patch or minor versions.

Fortunately we also require cargo check to pass too so we'll catch that!

would it make sense to version oci-spec separately from libcontainer / libcgroups?

Anyways! Thank you all for the work and accepting my PRs <3 eagerly looking forward to this release!!!

@nayuta723

Copy link
Copy Markdown
Contributor

Thank you for your feedback!

would it make sense to version oci-spec separately from libcontainer / libcgroups?

The background here is that oci-spec is not specific to youki and was split out as an external package. In addition, oci-spec-rs includes not only the runtime specification, but also the image and distribution specifications, so we have treated it as a separate external package so far.
From a versioning perspective, what would be the main motivation for keeping its version aligned with libcontainer and libcgroups?

If breaking changes are included, i would personally prefer if those came with a major version bump to match with semver. We use renovate to automatically suggest version changes. We merge changes without much checking if they are patch or minor versions.

Also, youki currently follows the v0.y.z versioning scheme, which allows a more flexible approach to breaking changes during initial development. Since a minor version bump would still be consistent with semver, I am considering that approach for this release.

@JosiahParry

Copy link
Copy Markdown
Contributor

ope! I missed that oci-spec is already versioned differently! Minor version bump very welcomed!

Right now our product is in the last stages of putting the polish on it. One of the last features we need before we're comfortable is being able to run it in docker. v0.7.0 will get us there 🚀!

Thank you <3

@saku3

saku3 commented Jul 19, 2026

Copy link
Copy Markdown
Member

@nayuta723

For reference, this release PR is configured to create the v0.7.0 tag, but the package versions and release URLs are currently being updated to 0.6.1.

To release this as v0.7.0, we need to apply a version update equivalent to the following PR:

#3424

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants