Sp 5786/enable publishing to npm#148
Merged
Merged
Conversation
adgad
reviewed
Feb 3, 2026
| ## Releasing | ||
|
|
||
| (TODO: no good release process yet) | ||
| A single semantic change to the content tree is usually split across multiple pull requests, with Go and JS changes implemented by separate teams. It is important therefore that releases are coordinated across C&M, Spark and CP to ensure that each release contains all the changes required to support the new version of the content tree. |
Collaborator
There was a problem hiding this comment.
praise: these are helpful docs!
Contributor
There was a problem hiding this comment.
praise: 👍 thanks for the docs
adgad
previously approved these changes
Feb 3, 2026
debugwand
reviewed
Feb 3, 2026
epavlova
reviewed
Feb 5, 2026
| (TODO: no good release process yet) | ||
| A single semantic change to the content tree is usually split across multiple pull requests, with Go and JS changes implemented by separate teams. It is important therefore that releases are coordinated across C&M, Spark and CP to ensure that each release contains all the changes required to support the new version of the content tree. | ||
|
|
||
| Before making a release you will also need to raise a pull request to increment the package.json version number, this should be made in its own PR so that at least one member of each team can approve it. Please get sign-off in the [#dynamic-storytelling-team](https://financialtimes.enterprise.slack.com/archives/C035P5DCHMH) slack channel and share this PR there. Releases are then made via GitHub Releases: they must include a SemVer tag `vX.Y.Z` which matches the one within the package json. The release notes should be completed to communicate what changed in the release. Cutting a release will trigger CI to publish to npm for JS consumers. Go consumers can depend on the new git tag as the module version. |
Contributor
There was a problem hiding this comment.
thought (non-blocking): Would it make sense to create a dedicated channel for communicating content tree changes? I’m pretty sure the Specialists would also find it useful to follow those updates.
| ## Releasing | ||
|
|
||
| (TODO: no good release process yet) | ||
| A single semantic change to the content tree is usually split across multiple pull requests, with Go and JS changes implemented by separate teams. It is important therefore that releases are coordinated across C&M, Spark and CP to ensure that each release contains all the changes required to support the new version of the content tree. |
Contributor
There was a problem hiding this comment.
praise: 👍 thanks for the docs
debugwand
approved these changes
Feb 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
We need a way to version and distribute our types and schemas so consumers don’t have to pin to commits, and so we can coordinate breaking changes. Proposal.
What?
Here are the results from running the new CI workflow with --dry-run Results