Skip to content

Commit 845aec6

Browse files
brunozoricclaude
andcommitted
docs: update versioning docs to reflect changesets workflow
README and AGENTS.md still described the old conventional-commit publish pipeline. Updated to document the Changesets workflow and removed the hardcoded version from the AGENTS.md package.json example. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent d38beb4 commit 845aec6

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

AGENTS.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -918,7 +918,7 @@ import { createAbstraction } from "~/common/index.js";
918918
```json
919919
{
920920
"name": "@webiny/stdlib",
921-
"version": "0.0.1",
921+
"version": "<managed by changesets>",
922922
"type": "module",
923923
"exports": {
924924
".": { "import": "./dist/index.js", "types": "./dist/index.d.ts" },

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,4 +57,4 @@ The package is ESM-only and ships three subpath exports. Because each is a separ
5757

5858
## Versioning
5959

60-
The package version in `package.json` is always `0.0.0`. The real version is injected at publish time by the release pipeline using conventional commits: `feat` bumps the minor, everything else (`fix`, `chore`, `refactor`, …) bumps the patch. There are no major version bumps — breaking changes may land on minor releases.
60+
Versioning and publishing are managed by [Changesets](https://github.com/changesets/changesets). The version in `package.json` is the real published version, bumped automatically when a version PR is merged. To record a version bump, run `yarn changeset` before opening a PR. There are no major version bumps — breaking changes may land on minor releases.

0 commit comments

Comments
 (0)