Repository navigation
chore: declare r3.2 rc release (Sync26) - #192
Merged
clundie-CL merged 3 commits intoOct 16, 2026
Merged
Conversation
Advance the Sync26 release intent from the r3.1 RC to the r3.2 public release. Both APIs stay at 0.3.0 (initial public, major version 0). Commonalities r4.3 / ICM r4.2 pins unchanged.
clundie-CL
marked this pull request as ready for review
October 7, 2026 12:47
clundie-CL
requested review from
benhepworth,
caubut-charter and
mayur007
as code owners
October 7, 2026 12:47
benhepworth
requested changes
Oct 16, 2026
benhepworth
left a comment
benhepworth
left a comment
Contributor
There was a problem hiding this comment.
also update the description from public release to final release candidate
Co-authored-by: Ben Hepworth <125334035+benhepworth@users.noreply.github.com>
clundie-CL
changed the title
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.
What type of PR is this?
What this PR does / why we need it:
Declares r3.2 as a second release candidate for the Sync26 meta-release, as agreed at the 2026-10-16 sub-project call:
target_release_tag:r3.1→r3.2(same release cycle, so the second number increments)target_release_type: stayspre-release-rcnetwork-access-devicesandnetwork-access-domains:target_api_statusstaysrc, andtarget_api_versionstays0.3.0. The snapshot will produce0.3.0-rc.2for both APIs.mainhas changed since r3.1 (0.3.0-rc.1), so a new RC lets release management review those changes before the public release, rather than going straight from rc.1 to public. Once r3.2 is signed off, a follow-uprelease-plan.yamlPR will declare the r3.3 initial public release (0.3.0) with no further content changes.Which issue(s) this PR fixes:
None. This is the release-intent step that precedes
/create-snapshoton the r3.2 Release Issue.Does this PR introduce a breaking change?
Special notes for reviewers:
0.3.0-rc.1), all allowed within 0.x and none of which changetarget_api_version:AccessDetailenum values removed). Thread was never implementable as specified, and no consumers outside the sub-project depend on it. Restoring it is tracked in Restore and Complete Thread Support #183.writeOnlyfields out of response documentation.404from theGET /network-access-devicescollection, consistent with the other collection endpoints.r4.3, ICMr4.2, the same baseline as r3.1.Changelog input
Additional documentation
This section can be blank.