Repository navigation
OIL 8: v2.0.0 is the merge of #10 - #11
Merged
Merged
Conversation
The code of #9, with the template's v0.5.1, without which the release could not be built while GitHub's runners reached no mirror of Canonical. OIL 8.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TimerTwo 2.0.0 is released: the tag
v2.0.0sits on the merge of #10, with its .zip on the release. This records it in item 8 of OIL.md.What changes for a user
Nothing in the library. OIL.md names the merge of #10 as the tagged state, not that of #9 as it said.
Why
#10 has the code of #9 and the template's v0.5.1. Without it the release could not have been built while GitHub's runners reached no mirror of Canonical, as on 2026-11-11.
How it was checked
The CI of
mainpassed at the merge of #10 before it was tagged, andrelease.ymlbuilt the release from the tag.