Skip to content

Commit d7a1090

Browse files
Merge branch 'main' into SHAPE-7318-revert-changes-to-templates-to-allow-ci-to-pass
2 parents ee950ba + 0e8bc83 commit d7a1090

File tree

3 files changed

+15
-7
lines changed

3 files changed

+15
-7
lines changed

CONTRIBUTING.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -153,14 +153,15 @@ This will prompt you to select which package (`@storyblok/field-plugin` or `@sto
153153

154154
Once this pull request is reviewed and merged, you'll get a commit like [this](https://github.com/storyblok/field-plugin/commit/b4bd948ce3d26f0905352ddbe474ebc9e2f89159).
155155

156-
Then, go to [Releases](https://github.com/storyblok/field-plugin/releases) and create a new release. The title should follow the format `<PACKAGE-NAME>@<VERSION>`. Examples:
156+
Then, go to [Releases](https://github.com/storyblok/field-plugin/releases) and draft a new release:
157157

158-
- `@storyblok/[email protected]`
159-
- `@storyblok/[email protected]`
158+
- Create a tag with the format `<PACKAGE-NAME>@<VERSION>`; for example, `@storyblok/[email protected]` and `@storyblok/[email protected]`
159+
- Set the title to the same name.
160+
- Generate release notes, and ensure that the content is accurate; for example, check that there are no missing bullet points, and check that library changes should not be listed in CLI release notes.
160161

161-
You can find a sample release [here](https://github.com/storyblok/field-plugin/releases/tag/%40storyblok%2Ffield-plugin-cli%400.0.1-beta.2). Make sure you write accurate changelogs, ensuring that library changes are not included in a CLI release and vice versa.
162+
You can find a sample release [here](https://github.com/storyblok/field-plugin/releases/tag/%40storyblok%2Ffield-plugin-cli%400.0.1-beta.2).
162163

163-
Once a release is created, one of the two GitHub Actions - [.github/workflows/npm-publish-library.yml](https://github.com/storyblok/field-plugin/blob/main/.github/workflows/npm-publish-library.yml) or [.github/workflows/npm-publish-cli.yml](https://github.com/storyblok/field-plugin/blob/main/.github/workflows/npm-publish-cli.yml) - will run and deploy it to NPM.
164+
Once a release is created, one of the two GitHub Actions[.github/workflows/npm-publish-library.yml](https://github.com/storyblok/field-plugin/blob/main/.github/workflows/npm-publish-library.yml) or [.github/workflows/npm-publish-cli.yml](https://github.com/storyblok/field-plugin/blob/main/.github/workflows/npm-publish-cli.yml)will run and deploy the corresponding package to npm.
164165

165166
### Order of releases
166167

packages/field-plugin/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@storyblok/field-plugin",
3-
"version": "1.3.0",
3+
"version": "1.4.0",
44
"description": "SDK for creating Field Plugins for Storyblok.",
55
"sideEffects": false,
66
"files": [

yarn.lock

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1871,7 +1871,14 @@ __metadata:
18711871
languageName: unknown
18721872
linkType: soft
18731873

1874-
"@storyblok/[email protected], @storyblok/field-plugin@workspace:*, @storyblok/field-plugin@workspace:packages/field-plugin":
1874+
"@storyblok/field-plugin@npm:1.3.0":
1875+
version: 1.3.0
1876+
resolution: "@storyblok/field-plugin@npm:1.3.0"
1877+
checksum: 6b48a5c2f712ba412fbf904567b1292be44f8184c1ad7681be4b8102e22b8d188bd8e65e20edad4a196cd45cc66eb3314187963babe1b9f203250df572836be2
1878+
languageName: node
1879+
linkType: hard
1880+
1881+
"@storyblok/field-plugin@workspace:*, @storyblok/field-plugin@workspace:packages/field-plugin":
18751882
version: 0.0.0-use.local
18761883
resolution: "@storyblok/field-plugin@workspace:packages/field-plugin"
18771884
dependencies:

0 commit comments

Comments
 (0)