chore: version packages - #147
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
July 30, 2026 09:03
119fb30 to
c0927b1
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 30, 2026 09:45
c0927b1 to
394f545
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 30, 2026 09:45
394f545 to
1ad6eaf
Compare
rubenhensen
approved these changes
Jul 30, 2026
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
postguard-website@1.8.2
Patch Changes
e57e598: Mirror the Outlook add-in manifest from the monorepo's releases instead of the standalone repository, filtered to
outlook-addin-v*tags so releases of other packages in the shared namespace are not mistaken for add-in releases.outlook-addin-v1.0.0is published, so the mirror expects a matching release and finding none fails loudly rather than being reported as a state to wait out. The error names both plausible causes, since they call for opposite fixes: the release having scrolled out of the 50-release lookback window — which will happen eventually with nothing wrong, because the tag namespace is shared with@e4a/pg-js's far more frequent changesets releases — or the tag pattern, repo, or published state being wrong.