Repository navigation
ci: publish plugins to the EmDash registry after npm - #18
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 4e30da7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
emdash-release.yml comes from `emdash-plugin release setup` (plugin-cli 0.12.0, Changesets trigger) and runs after the npm publish job with the packages Changesets published. Two changes to the generated file: - pnpm/action-setup v4 aborts when its `version: 11` differs from package.json's `packageManager` (pnpm@11.15.1), so the input is gone and the action reads packageManager. - Build and publish run in separate jobs. The build job hands the bundle over as an artifact; the publish job only downloads it, attests it and runs the release action. The npm publish job gets the `npm` environment, so the trusted publisher on npmjs.com can require it. analytics: the registry refuses a profile description over 140 graphemes (ours had 202) and bundles a `screenshots/` folder whole, which took the bundle to 1,016 KB against a 256 KB limit. The description is shorter and the listing images move to `images/`, where they are uploaded as declared artifacts instead.
danielmlr
force-pushed
the
ci/emdash-registry-release
branch
from
September 27, 2026 21:13
c9df6bd to
4e30da7
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
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.
Publishes each npm release of a plugin to the EmDash registry as well. The first registry release will be analytics 0.2.1, when #17 is merged.
emdash-release.ymlis generated byemdash-plugin release setup(plugin-cli 0.12.0, Changesets trigger), andrelease.ymlcalls it after the npm publish job. The package profile@eisbachcode.de/analyticsand the publishing grant on releases.emdashcms.com already exist.Changes to the generated workflow
version: 11input is removed. pnpm/action-setup v4 aborts when that value is not exactly thepackageManagervalue frompackage.json(pnpm@11.15.1). Without the input, the action readspackageManager.emdash-cms/emdash/apps/release-action@mainstays unpinned, as generated. EmDash runs the release service that action talks to.Other changes
release.yml: the npm publish job getsenvironment: npm, so the trusted publisher on npmjs.com can require it. The publish job also exposespublishedandpublished-packagesfor the caller job.descriptionis shortened from 202 to 136 characters, because the registry profile allows at most 140.emdash-plugin validateaccepts up to 1,024, so the failure only showed atrelease setup.screenshots/becomesimages/. The registry bundle includes ascreenshots/folder whole. That took the bundle to 1,016 KB against a 256 KB limit, and two images were over the 128 KB per-file limit. Images inimages/are uploaded as the listing images declared in the manifest. The README links move with them.AGENTS.mdnow documents the registry step, the token rule and both registry limits.Verified
emdash-plugin release planlocally with a published-packages list containing analytics and shared: selects onlyanalytics@0.2.0.emdash-plugin release prepare analytics@0.2.0 --out-dir .emdash-release: a 37.8 KB bundle containingREADME.md,backend.jsandmanifest.json, with the publisher DID from the manifest.PackageProfile).actionlintpasses on both workflows.emdash-plugin validate, build and typecheck pass for analytics.After merging
@eisbachcode/emdash-plugin-analyticsto require thenpmenvironment.screenshots/onmain, so its images break until 0.2.1 is out.