ci: release#1103
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
docs | a8be859 | May 20 2026, 02:28 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-perf-coordinator | a8be859 | May 20 2026, 02:27 PM |
github-actions
Bot
added
area/admin
area/auth
area/cloudflare
area/core
area/plugins
bot
size/M
labels
Contributor
Scope checkThis PR touches 30 files. PRs with a broad scope are harder to review. Please confirm the scope hasn't drifted beyond the intended change. If this scope is intentional, no action needed. A maintainer will review it. If not, please consider splitting this into smaller PRs. See CONTRIBUTING.md for contribution guidelines. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-i18n | a8be859 | May 20 2026, 02:27 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-demo-cache | a8be859 | May 20 2026, 02:28 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-playground | a8be859 | May 20 2026, 02:28 PM |
@emdash-cms/admin
@emdash-cms/auth
@emdash-cms/blocks
@emdash-cms/cloudflare
emdash
create-emdash
@emdash-cms/gutenberg-to-portable-text
@emdash-cms/x402
@emdash-cms/plugin-ai-moderation
@emdash-cms/plugin-atproto
@emdash-cms/plugin-audit-log
@emdash-cms/plugin-color
@emdash-cms/plugin-embeds
@emdash-cms/plugin-forms
@emdash-cms/plugin-webhook-notifier
commit: |
18 tasks
emdashbot
Bot
force-pushed
the
changeset-release/main
branch
from
56895d2 to
da69821
Compare
This was referenced May 19, 2026
ascorbic
added a commit
that referenced
this pull request
May 19, 2026
Restores the two changesets removed in #1105 (which existed only to flip changesets/action onto the publish path for the already-versioned 0.13.0). With 0.13.0 now published, these re-enter the version path: the next Release run bumps 0.13.0 -> 0.13.1 and refreshes the changeset-release PR (#1103), whose merge publishes 0.13.1 with the #1100/#1101 fixes documented. Files are byte-identical to their pre-#1105 state.
emdashbot
Bot
force-pushed
the
changeset-release/main
branch
from
da69821 to
c2dc560
Compare
18 tasks
ascorbic
added a commit
that referenced
this pull request
May 19, 2026
#1110 reintroduced these changesets, so changelog-github credited both to #1110/@ascorbic, dropping @jcheese1's credit for #1100. Add per-changeset pr/commit/author overrides (read by @changesets/changelog-github) so the regenerated release PR attributes #1100 to @jcheese1 and #1101 to @ascorbic with the original commits. Editing #1103 directly wouldn't survive the next force-push of changeset-release/main.
emdashbot
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
d48f677 to
62da5b8
Compare
emdashbot
Bot
force-pushed
the
changeset-release/main
branch
from
62da5b8 to
9721d6c
Compare
emdashbot
Bot
force-pushed
the
changeset-release/main
branch
from
9721d6c to
a8be859
Compare
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
@emdash-cms/admin@0.14.0
Minor Changes
3756168Thanks @ascorbic! - Renders the full registry package profile in the admin. The plugin detail page now shows the license (linked to spdx.org for single SPDX identifiers), keywords, all authors, all security contacts, and a link to the source repository. The browse cards show the license alongside the description.Patch Changes
#1101
e539731Thanks @ascorbic! - Fixes experimental registry navigation and allows the configured registry aggregator through the admin CSP.Updated dependencies [
3756168]:@emdash-cms/plugin-cli@0.3.0
Minor Changes
#1112
3756168Thanks @ascorbic! - Publishes the full profile block fromemdash-plugin.jsonc. First publish now writesname,description,keywords, multiple authors, and multiple security contacts to the package profile record, plus the sourcerepoURL to the release record — previously onlylicenseand a single author/security contact were sent.Deprecates the
--license,--author-*, and--security-*flags in favour of declaring these inemdash-plugin.jsonc. The flags still work and override the manifest when both are present; a deprecation warning is printed when they are used.Patch Changes
3756168]:@emdash-cms/registry-client@0.1.0
Minor Changes
#1112
3756168Thanks @ascorbic! - Validates aggregator responses at the read-side trust boundary inDiscoveryClient. Two layers run:uri,cid,did,slug,version, …):DiscoveryClientnow routes every call through@atcute/client's schema-validating.call()against the aggregator method's output lexicon. Request params are validated too. A non-conforming envelope throwsClientValidationError.profile/releaserecords (typedunknownby the aggregator lexicon because they are relayed verbatim from publisher repos under a different lexicon namespace): nowsafeParse'd againstcom.emdashcms.experimental.package.profile/release. A conforming record is returned as the typed lexicon shape; a non-conforming one is surfaced asnullso one bad record doesn't fail an entire search page.Refines the return types from
unknowntoPackageProfile.Main | null/PackageRelease.Main | null(new exportedValidatedPackageView/ValidatedReleaseView/ValidatedSearchPackages/ValidatedListReleasestypes). Callers must null-check. The registry install handler now fails closed when the aggregator returns a release record that does not conform to its lexicon.Validation is structural only — the lexicon's
uriformat permits non-HTTP schemes, so UI rendering these URLs still applies its own scheme allow-list.@emdash-cms/auth-atproto@0.2.7
Patch Changes
cf85941,cf85941,3756168]:@emdash-cms/cloudflare@0.14.0
Patch Changes
cf85941,cf85941,3756168]:emdash@0.14.0
Patch Changes
#1100
f753dbaThanks @jcheese1! - Resolve bare local media IDs in media fields before falling back to external URLs.#1101
e539731Thanks @ascorbic! - Fixes experimental registry navigation and allows the configured registry aggregator through the admin CSP.#1112
3756168Thanks @ascorbic! - Validates aggregator responses at the read-side trust boundary inDiscoveryClient. Two layers run:uri,cid,did,slug,version, …):DiscoveryClientnow routes every call through@atcute/client's schema-validating.call()against the aggregator method's output lexicon. Request params are validated too. A non-conforming envelope throwsClientValidationError.profile/releaserecords (typedunknownby the aggregator lexicon because they are relayed verbatim from publisher repos under a different lexicon namespace): nowsafeParse'd againstcom.emdashcms.experimental.package.profile/release. A conforming record is returned as the typed lexicon shape; a non-conforming one is surfaced asnullso one bad record doesn't fail an entire search page.Refines the return types from
unknowntoPackageProfile.Main | null/PackageRelease.Main | null(new exportedValidatedPackageView/ValidatedReleaseView/ValidatedSearchPackages/ValidatedListReleasestypes). Callers must null-check. The registry install handler now fails closed when the aggregator returns a release record that does not conform to its lexicon.Validation is structural only — the lexicon's
uriformat permits non-HTTP schemes, so UI rendering these URLs still applies its own scheme allow-list.Updated dependencies [
cf85941,3756168,3756168]:create-emdash@0.14.0
Patch Changes
792f73cThanks @ascorbic! - PinspackageManagerfor pnpm-scaffolded sites so a recent enough pnpm is used (settings-onlypnpm-workspace.yamlrequires pnpm 10.5+). For npm, yarn, or bun selections the field is stripped so corepack doesn't force pnpm on a non-pnpm user.@emdash-cms/plugin-embeds@0.1.15
Patch Changes
cf85941,cf85941,3756168]:@emdash-cms/auth@0.14.0
@emdash-cms/blocks@0.14.0
@emdash-cms/gutenberg-to-portable-text@0.14.0
@emdash-cms/x402@0.14.0
@emdash-cms/fixture-perf-site@0.0.10
Patch Changes
cf85941,cf85941,3756168]:@emdash-cms/perf-demo-site@0.0.10
Patch Changes
cf85941,cf85941,3756168,3756168]:@emdash-cms/cache-demo-site@0.0.10
Patch Changes
cf85941,cf85941,3756168,3756168]: