Authoring changesets
Update the changeset already introduced by the PR. If there is none, create one
.changeset/<descriptive-name>.md for the complete PR:
---
"effect": patch
"@effect/affected-package": patch
---
Fix `Effect.cachedInvalidateWithTTL` caching a stale result when invalidated while the effect is running. Write one short sentence, usually under 25 words, that names the changed API and states what consumers will notice. That sentence is the whole entry unless the change is breaking or consumers must migrate.
Leave out how the change works: internal modules, algorithms, data structures, refactors, motivation, benchmarks, test coverage, and development history. They belong in the PR description. Cut any sentence a consumer would not act on.
- Bad: "Rework the
MemoMaplookup soLayer.providechecks identity before building, adding a cache keyed by layer reference and tests for shared layers." - Good: "Fix composed layers being rebuilt for every parent that references them."
Add detail only for a break or required migration: what existing code must change and how. Use compact bullets, one break per bullet, when several breaks need migration steps. Several non-breaking fixes or additions still share one sentence.
List every directly affected published package. Do not list packages merely
because they share the fixed release group in .changeset/config.json.
Choose the bump from current release policy:
- APIs tagged
@stability stable, and APIs without a stability tag, follow strict semver:patchfor compatible fixes,minorfor compatible additions, andmajorfor breaks. - For APIs tagged
@stability unstable, usepatchfor compatible fixes and new features. Only a break isminor. - For APIs tagged
@stability experimental, usepatchfor fixes, new features, and breaks. - When a PR touches APIs at several stability levels, use the highest bump any of them requires.
- Use
majoronly when a maintainer has approved a major release. - The release queue retargets PRs with
minorchangesets tov4/next-minorand PRs withmajorchangesets tov4/next-major. Choose the level the change requires, not the branch you want it to land on. - Ask when release intent is ambiguous.
Use a ### Breaking changes section when several breaks need separate
scanning. Include before/after examples only when they materially clarify
migration.
Validate frontmatter against published package names and inspect nearby current
changesets for release convention. Do not copy the length of longer entries.
Never run changeset-version or changeset-publish as contributor validation.