Prepare the 0.6.0 release - #26
Merged
Merged
Conversation
Version bumped in the five places RELEASING.md lists — the podspec, the four README install snippets, the changelog heading and the packaging script's usage — plus COMPATIBILITY.md's column header and RELEASING.md's own worked example, which that list misses. The changelog gains a Changed section. `logout()` and `stop()` can now block their caller for up to a second while a call finishes tearing down, and a host calling either from a CXEndCallAction handler needs to know before it upgrades, not after. Buried at the end of a Fixed bullet it was not findable. Package.swift is untouched: the PJSIP binary is unchanged, so the pinned 2.17-opus-sha256.2 release asset and its checksum still apply and there is nothing to repackage. The field-test record is retitled for 0.6.0 and still reads "not run", now saying outright that the tag must not be cut until it is filled in. Scenario 4 is called out as the one to run first: it is the only scenario with a reported field failure behind it, and the decline-path fix is the largest behavioural change in the release. Verified: 131 tests, TSan clean, device and strict-concurrency builds, PJSIP binary verification, `pod lib lint` against the new version.
Closed
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.
The 0.6.0 version bump missed the #24 merge: that PR was squash-merged before
this commit was pushed to its branch, so
maincarries the code but none ofthe release metadata.
spec.versionis still0.5.0, COMPATIBILITY still says0.6's predecessor, the README install snippets still point at 0.5.0, and the
changelog section is still
## [Unreleased].The
0.6.0tag was already pushed against that state, which is the exactfailure
RELEASING.mdwarns about —spec.sourceresolvestag: spec.version.to_s, sopod trunk pushfails on the mismatch. The tag isbeing deleted and recreated on top of this merge; no GitHub release was cut and
nothing was published from it.
This is
d582b58cherry-picked ontomain, unchanged.Verified on this branch:
pod lib lintpasses against 0.6.0, and the packagetest suite is green.
The field-test record in FIELD-TESTING.md is still empty. It is titled for
0.6.0 and says the tag must not be cut until it is filled in — that pass is
still owed, and scenario 4 is the one to run first.