feat!: install and update msd from git release tag #1

Merged

jakub merged 3 commits from feat/stable-release-channel into next 2026-10-09 08:55:15 +00:00

Conversation 2 Commits 3 Files Changed 144 +540 -716

jakub commented 2026-10-09 08:33:39 +00:00

Owner

Copy Link

MSD is not published to npm, so /msd-update and the SessionStart update
check could never find a release. Releases are now vX.Y.Z git tags plus a
stable branch:

• check-latest-version reads release tags via git ls-remote against the
  baked repository URL (latest = highest stable tag, next = incl. -rc)
• /msd-update reruns the bootstrap installer pinned to the checked tag and
  reads the changelog from that tag
• bootstrap.sh defaults to the stable branch and supports --local/--global
• package identity: changelog URL on stable, manual install via
  msd.golem15.com
• README quickstart and update how-to describe the one-line installer
• track the repo-root CLAUDE.md

Emitted-Drift-Ack-Growth: update.md — the update flow now explains the git-tag release lookup and pins the bootstrap installer to the checked tag, replacing the npm/npx wording

MSD is not published to npm, so /msd-update and the SessionStart update check could never find a release. Releases are now vX.Y.Z git tags plus a stable branch: - check-latest-version reads release tags via git ls-remote against the baked repository URL (latest = highest stable tag, next = incl. -rc) - /msd-update reruns the bootstrap installer pinned to the checked tag and reads the changelog from that tag - bootstrap.sh defaults to the stable branch and supports --local/--global - package identity: changelog URL on stable, manual install via msd.golem15.com - README quickstart and update how-to describe the one-line installer - track the repo-root CLAUDE.md Emitted-Drift-Ack-Growth: update.md — the update flow now explains the git-tag release lookup and pins the bootstrap installer to the checked tag, replacing the npm/npx wording

jakub added 1 commit 2026-10-09 08:33:39 +00:00

feat: install and update msd from git release tags, not npm ... f8614b5c20

MSD is not published to npm, so /msd-update and the SessionStart update
check could never find a release. Releases are now vX.Y.Z git tags plus a
stable branch:

- check-latest-version reads release tags via git ls-remote against the
  baked repository URL (latest = highest stable tag, next = incl. -rc)
- /msd-update reruns the bootstrap installer pinned to the checked tag and
  reads the changelog from that tag
- bootstrap.sh defaults to the stable branch and supports --local/--global
- package identity: changelog URL on stable, manual install via
  msd.golem15.com
- README quickstart and update how-to describe the one-line installer
- track the repo-root CLAUDE.md

Emitted-Drift-Ack-Growth: update.md — the update flow now explains the git-tag release lookup and pins the bootstrap installer to the checked tag, replacing the npm/npx wording

jakub added 2 commits 2026-10-09 08:35:13 +00:00

docs: add changesets for the msd fork, runtime removal and tag-based updates a4dd615659

chore: release 2.0.0 294039720c

gitea-actionsbot commented 2026-10-09 08:35:46 +00:00

Copy Link

Closing — no pre-approved issue

Thanks for your interest in MSD! This PR was closed automatically because it does not link an issue.

MSD requires a pre-approved issue before any PR. The PR must link an issue in this repository that carries a maintainer-applied approval label — approved-feature, approved-enhancement, or confirmed-bug. Opening your own issue or citing an unrelated number is not enough: the label is applied by maintainers after triage.

What to do

1. Open an issue describing the change (bug, enhancement, or feature).
2. Wait for a maintainer to approve it (confirmed-bug, approved-enhancement, or approved-feature).
3. Open a new PR using the matching template, with Closes #<issue> in the body.

See CONTRIBUTING.md for the full process. If you believe this was closed in error, comment here and a maintainer can reopen it.

<!-- msd-auto-close-unsolicited --> ## Closing — no pre-approved issue Thanks for your interest in MSD! This PR was closed automatically because it does not link an issue. **MSD requires a pre-approved issue before any PR.** The PR must link an issue in this repository that carries a maintainer-applied approval label — `approved-feature`, `approved-enhancement`, or `confirmed-bug`. Opening your own issue or citing an unrelated number is not enough: the label is applied by maintainers after triage. ### What to do 1. [Open an issue](https://github.com/golem15/msd-core/issues/new/choose) describing the change (bug, enhancement, or feature). 2. Wait for a maintainer to approve it (`confirmed-bug`, `approved-enhancement`, or `approved-feature`). 3. Open a new PR using the matching template, with `Closes #<issue>` in the body. See [CONTRIBUTING.md](https://github.com/golem15/msd-core/blob/main/CONTRIBUTING.md) for the full process. If you believe this was closed in error, comment here and a maintainer can reopen it.

gitea-actionsbot closed this pull request 2026-10-09 08:35:46 +00:00

gitea-actionsbot commented 2026-10-09 08:36:30 +00:00

Copy Link

PR title needs the issue-ref convention

feat: install and update msd from git release tags, not npm

PR title must follow type(#<issue>): summary. The type must come first (no leading tags like [security]) and the scope must carry the linked issue ref so the release changelog links to it. Examples: fix(#1542): roadmap rollback, feat(#39)!: drop legacy flag, enhance(#1549): add PR-title validator.

How to fix: click "Edit" next to the PR title above and retitle it
as type(#<issue>): summary. No need to recreate the PR — this check
re-runs when you edit the title.

Why this is enforced

The release changelog is built from PR titles. A leading tag mis-files
the entry into the wrong section, and a scope without (#<issue>) leaves
the changelog line with no link back to the issue. See issue #1549.

<!-- pr-title-validator --> ### PR title needs the issue-ref convention `feat: install and update msd from git release tags, not npm` PR title must follow `type(#<issue>): summary`. The type must come first (no leading tags like `[security]`) and the scope must carry the linked issue ref so the release changelog links to it. Examples: `fix(#1542): roadmap rollback`, `feat(#39)!: drop legacy flag`, `enhance(#1549): add PR-title validator`. **How to fix:** click "Edit" next to the PR title above and retitle it as `type(#<issue>): summary`. No need to recreate the PR — this check re-runs when you edit the title. <details><summary>Why this is enforced</summary> The release changelog is built from PR titles. A leading tag mis-files the entry into the wrong section, and a scope without `(#<issue>)` leaves the changelog line with no link back to the issue. See issue #1549. </details>

jakub referenced this issue from a commit 2026-10-09 08:53:58 +00:00

chore: drop upstream gsd issue and pr governance

jakub changed title from feat: install and update msd from git release tags, not npm to feat!: install and update msd from git release tag 2026-10-09 08:54:48 +00:00

jakub reopened this pull request 2026-10-09 08:54:52 +00:00

jakub merged commit d1a3a31731 into next 2026-10-09 08:55:15 +00:00

jakub referenced this issue from a commit 2026-10-09 08:55:17 +00:00

Merge pull request 'feat!: install and update msd from git release tag' (#1) from feat/stable-release-channel into next

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

260 jakub lucas

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: golem15/msd-core#1