Say when an integration syncs Core, and why not sooner - #22
Merged
Merged
Conversation
The rule was implied by two scripts and written down nowhere: an integration syncs as part of its own release, because a repository that re-syncs when Core publishes has aligned its source and nothing a user can install.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
jsray | 9b7be5f | Commit Preview URL Branch Preview URL |
Sep 06 2026, 11:24 AM |
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 rule two scripts already implement, written down where the boundary is described.
tools/sync-core.shandtools/check-core-freshness.mjsbetween them decide when an integration's vendored snapshot is allowed to be behind, butdocs/projects.mdsaid only that Core assets "flow into plugin repositories" — nothing about timing. Reading the repositories, the natural inference is the wrong one: that a snapshot two Core versions behind is an outstanding chore. It is not. A.vsix, a plugin zip and the source archive GitHub attaches to a tag all freeze whatever snapshot they were built from, so re-syncing the moment Core publishes aligns the source and nothing a user can install.So the doc now states the rule and the reason, and names the two modes the freshness check actually has: advisory between releases, strict at the packaging gate. It also names the exception — a security-grade Core release is the one case that should not wait for the next feature release.
Documentation only; no runtime or tooling change.