Repository navigation
chore: version packages - #9444
Merged
Merged
Conversation
gram-bot
Bot
force-pushed
the
changeset-release/main
branch
from
November 21, 2026 18:52
4473518 to
9a40a45
Compare
gram-bot
Bot
force-pushed
the
changeset-release/main
branch
from
November 21, 2026 19:52
9a40a45 to
9260d9b
Compare
There was a problem hiding this comment.
Scheduled release approval. Required checks are green on 9260d9b.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
dashboard@0.154.0
Minor Changes
server@2.40.0
Minor Changes
GRAM_PARTITIONsetting (usoreu) naming the partition they run in. There is no default: each refuses to start when it is missing, empty or unknown, so a deployment cannot silently run as the wrong partition. Each tags its logs withgram.partition; the server and pystreams also put it on their traces and metrics.gram versionand help output work without it. Local development setsGRAM_PARTITION=usinmise.toml.GRAM_STAFF_ORGANIZATION_IDsetting instead of a hardcoded organization. Outside local development each process refuses to start when it is missing or matches no organization in its database. Audit log staff masking, the organization whitelist endpoint, OpenRouter credit limit exemption, daily connection outcomes and the hooks rollout canary (in the plugin publisher and the admin dashboard) all use it. The Vanta evidence sink sends the deployment's HTTPS server origin as each resource'sexternalUrl.tunnel@0.3.0
Minor Changes
GRAM_PARTITIONsetting (usoreu) naming the partition they run in. There is no default: each refuses to start when it is missing, empty or unknown, so a deployment cannot silently run as the wrong partition. Each tags its logs withgram.partition; the server and pystreams also put it on their traces and metrics.gram versionand help output work without it. Local development setsGRAM_PARTITION=usinmise.toml.