ci: pack ioxide.timer - #214
Merged
Merged
Conversation
The pack steps are one per project and hand-written, so a new package is not picked up by adding it to the solution - ioxide.slnx builds it and the release then shipped everything except it. Which is what happened to 0.7.211: the SubmitTimeout in core went out, the client over it did not. Checked the rest against the tree while here; every project carrying a PackageId now has a pack step.
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
1 participant
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.
Follow-up to #213, which merged before this reached it.
ioxide.timeris inioxide.slnx, so CI builds it, and it has aPackageIdand a version. But the pack steps are one hand-written block per project, so the release shipped everything except the new package:SubmitTimeoutwent out inioxide0.7.211 and the client over it did not.One step added. Checked the rest of the tree while here: 12 packable projects, 0 without a pack step.
The version on main is already 0.7.211 and that version does not exist for this package id, so it publishes on merge;
--skip-duplicatecovers the eleven that are already out.