@monup/release

Package publishing for the Monup release step.

Workflow Role

@monup/release is the publish stage of the workflow. In the default Monup flow, this is usually the CI step that runs after local version and changelog work has already been reviewed.

Main Exports

• publish(): publish one package manifest.
• publishPackages(): publish all detected packages with shared context.
• listPublishedVersions(): inspect already published versions.
• setupJsrPackages(): create JSR package entries and apply shared or per-package settings.
• resolveReleaseOptions(): normalize release options.
• defaultReleaseOptions: shared release defaults.

One logical package can publish more than once when it has multiple manifest files, because Monup creates one publish target per packageFile.

Notes

• Publish targets are inferred from the package manifest being handled.
• Registry and package-manager handling are resolved internally.
• dryRun behavior depends on the resolved release options and CI context.
• setupJsrPackages() is intended for local JSR package preparation and accepts an explicit token, while the CLI now defaults to interactive browser authorization and only falls back to JSR_TOKEN in non-interactive mode.

Example

import { publishPackages, setupJsrPackages } from '@monup/release';

await publishPackages(packages, releaseOptions, {
	dryRun: true,
	isCI: false,
});

await setupJsrPackages(packages, {
	githubRepository: {
		owner: 'monup',
		name: 'monup',
	},
	readmeSource: 'readme',
	runtimeCompat: {
		node: true,
		deno: true,
	},
	packageOverrides: {
		'@monup/cli': {
			description: 'CLI entry point for Monup.',
		},
	},
});

Related Packages

• @monup/workspace: provides detected packages and manifest paths.
• @monup/options: provides resolved release options.
• @monup/github: usually runs after publishing.