Skip to content

Releases: fuma-nama/tegami

tegami@1.0.0-beta.3 (beta)

28 Jun 18:20
172eaa2

Choose a tag to compare

Pre-release

Improve GitHub release notes (d55a3a0)

The release notes can now display related PRs & contributors.

Support go.publish option (167dea0)

Decide whether a Go package should be published via the go.publish option, default to true.

Drop MDAST dependencies (7d8091b)

Tegami only requires extracting headings and preserves formatting, a regex alternative is lighter, better, and faster.

Add GitLab plugin (0501ffd)

Tegami now includes a GitLab plugin with version merge requests, GitLab releases, tag handling, and release note links for commits and related merge requests.

tegami@1.0.0-beta.2 (beta)

28 Jun 09:53
37ae6cd

Choose a tag to compare

Pre-release

Change behaviour of publishPreflight hook (7cfb2cc)

Now only the first handler plugin will be considered, no longer merges results.

Replace preflight.publish with preflight.shouldPublish (7cfb2cc)

The publish checking will only happen at publish-time & plan resolve.

tegami@1.0.0-beta.1 (beta)

28 Jun 05:48
a93689d

Choose a tag to compare

Pre-release

Handle empty version fields in Cargo.toml & package.json (ee8716f)

No longer bump versions when version field is not defined.

Fix replaying changelogs showing in PR body (ee8716f)

No longer show replay-only changelogs in PR previews.

Show bumped packages of each changelog (84ec942)

The PR preview body now show the bumped packages of each changelog, in a collapsible.

tegami@1.0.0-beta.0 (beta)

27 Jun 16:25
ed9d377

Choose a tag to compare

Pre-release

Generate dist tag for npm in prerelease mode (24a7894)

npm publish now requires tag for prerelease versions.

Plugin afterPublish no longer fired for skipped packages (ab56795)

The afterPublish hook of plugins will no longer be fired for skipped packages.

Add support for Golang (cd7ff31)

Experimental plugin available at /plugins/go.

Ready for v1 (bf8e66a)

This marks all existing APIs as stable & safe to use.

Support function packages option (7c08e3b)

The packages option can now return package options dynamically.

Include packages without version (c266203)

Previously, packages without a version field defined in package.json or Cargo.toml will be ignored from graph, now those packages will be included.

This may add unwanted packages into versioning, please update your ignore config if needed.

Fix prerelease tag switching (3aa54d1)

Switch prerelease tag without triggering another bump.

Auto replay when prerelease is configured (e311fe7)

No longer need to write replay conditions manually.

tegami@0.2.1

26 Jun 11:53
12e5708

Choose a tag to compare

Fix failing checks for Git tags (7ab67bd)

Fixed a bug that causes publish plan status checking to fail.

Fix lifecycle hooks for Bun (7ab67bd)

Tegami used bun pm pack workaround for Bun, but it doesn't run lifecycle hooks. Tegami now runs the hooks same as other setups.

tegami@0.2.0

26 Jun 10:21
d36f969

Choose a tag to compare

Redesign GitHub plugin options (ff72ecd)

GitHub release and Version Packages PR settings are now top-level options:

  • eagerReleaserelease: { eager: true }
  • onCreateReleaserelease.create
  • onCreateGroupedReleaserelease.createGrouped
  • onCreateVersionPullRequestversionPr.create
  • cli.versionPrversionPr (use forceCreate: true to enable locally)

Set release: false to disable GitHub release creation.

Add check-publish CLI command (05c098b)

tegami check-publish checks whether a publish lock has packages waiting to be published. It exits 0 when publishing is needed and 1 when it is not, so CI workflows can skip unnecessary steps without actually trying to publish packages.

if tegami check-publish; then
  # other commands
fi

Use HTTP APIs instead of CLI tools (bfc8d42)

GitHub releases, pull requests, and comments now use the GitHub REST API instead of the gh CLI. npm publish preflight checks the registry over HTTP instead of running npm view or pnpm view.

Git operations and package publishing still use their respective CLI tools.

Lock files update by default (bfc8d42)

updateLockFile now defaults to true for the npm and Cargo providers. Lockfiles are refreshed automatically after versioning unless you set updateLockFile: false.

v0.2 redesign (5e58344)

Tegami 0.2 separates versioning from publishing and renames several core types.

Publish lock replaces the publish plan file (5e58344)

tegami version now writes .tegami/publish-lock.yaml instead of a JSON publish plan file.

  • Config option planPath is now lockPath (default: .tegami/publish-lock.yaml).
  • The lock uses YAML namespaces (core:packages, core:changelogs, npm:packages, …) instead of a single JSON document.
  • Packages must have updated: true in the lock to be published. New packages added after versioning are excluded until the next release cycle.

Draft and publish plan API (5e58344)

v0.1 v0.2
DraftPlan Draft
PackagePlan PackageDraft
createDraftPlan() createDraft()
draft.getPackagePlans() draft.getPackageDrafts()
JSON PlanStore on disk PublishLock YAML on disk + in-memory PublishPlan at publish time
publish()PublishResult publish()PublishPlan | "skipped"
cleanupPublishPlan() cleanupPublishLock()

PublishPlan is built in memory when you call publish(). It is not written to disk.

Plugin hook renames (5e58344)

v0.1 v0.2
initPlan initDraft
applyPlan applyDraft
cli.publishPlanCreated cli.draftCreated
cli.publishPlanApplied cli.draftApplied
createRegistryClient removed — use publishPreflight / publish on plugins
RegistryClient removed

New hooks:

  • initPublishLock — write plugin data into the publish lock when a draft is applied.
  • initPublishPlan — enrich the in-memory publish plan from the lock (e.g. git tags, npm dist-tags).
  • publishPreflight — check registries and declare publish order before publishing.
  • resolvePlanStatus — report whether post-publish work (git tags, GitHub releases) is complete.

resolvePlanStatus, afterPublish, and afterPublishAll now receive a PublishPlan instead of PublishResult / PlanStore.

LogGenerator (5e58344)

Custom changelog generators now receive { pkg, packageDraft, draft } instead of { packageId, packageName, version, changelogs, plan, unstable_draft }.

Package options (5e58344)

packages.<name>.publish was removed from Tegami config. Control npm publishing with private: true or publishConfig in package.json instead.

GitHub plugin (5e58344)

GitHub release and Version Packages PR options moved to the top level:

  • eagerReleaserelease: { eager: true }
  • onCreateReleaserelease.create
  • onCreateGroupedReleaserelease.createGrouped
  • onCreateVersionPullRequestversionPr.create
  • cli.versionPrversionPr (use forceCreate: true to enable locally)

Release callbacks now receive { tag, pkg, plan } (or grouped equivalents) instead of PackagePublishResult. Set release: false to disable GitHub releases.

Support conventionalCommits option (ba05602)

When enabled, it generates changelogs from commits when you run tegami version.

tegami@0.1.6

24 Jun 18:15
b155598

Choose a tag to compare

Check GitHub release before creating (6e3edf5)

Prevent errors from conflicts.

tegami pr comment will ignore if there is no related PR (974629f)

tegami@0.1.5

24 Jun 09:58
42c2ea4

Choose a tag to compare

Use absolute path for bun pm pack (1afe6d6)

Somehow they're using project root and do not respect cwd at all.

tegami@0.1.4

24 Jun 04:54
226bd06

Choose a tag to compare

Fix handling for undefined bump types (650c898)

No longer cause unnecessary bumps for packages in prerelease.

Support group-level npm config (8f77c04)

Groups can now define npm config for member packages.

tegami@0.1.3

23 Jun 15:54
8729ee7

Choose a tag to compare

Hotfix error in GitHub plugin (6be511f)

Fix missing bump for changed prerelease option

Now, all changes to script-level package options (such as prerelease) will result in an update event, which ensures dependents are bumped correctly.

Use preferred package manager for publishing

This ensures the pm-specific protocols like workspace: are respected.

Support replay in changelog files

This allows changelog files to be replayed when a certain version released, this is useful if you want to replay changelogs when the first stable version lands, collecting changelogs from previous beta releases.

Generate replay automatically

When creating changelogs via tegami command, it will generate replay attribute automatically for packages in prerelease.

Support creating GitHub release eagerly

Without waiting for other packages, published packages will create a GitHub release.