@dbos-inc/dbos-sdk 5.3.5-preview → 5.3.6-test.0a362f9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/DEVELOPING.md +5 -2
- package/package.json +1 -1
package/DEVELOPING.md
CHANGED
|
@@ -25,7 +25,7 @@ node publish/make_release.mjs --patch 5.3
|
|
|
25
25
|
```
|
|
26
26
|
|
|
27
27
|
Pass `--no-publish` to tag and push without running the publish workflow.
|
|
28
|
-
You need the [GitHub CLI](https://cli.github.com/) logged in with
|
|
28
|
+
You need the [GitHub CLI](https://cli.github.com/) logged in with `repo` and `workflow` scopes, and permission to create branches and tags in this repo.
|
|
29
29
|
|
|
30
30
|
### Versions
|
|
31
31
|
|
|
@@ -39,4 +39,7 @@ Run it on any checkout to see what a build of the current branch would be versio
|
|
|
39
39
|
| anything else | `X.(Y+1).<commits since tag>-test.<sha>` | `test` |
|
|
40
40
|
|
|
41
41
|
The publish workflow runs on every push to `main`, so each merge publishes a preview.
|
|
42
|
-
Dispatching it manually on
|
|
42
|
+
Dispatching it manually on any other branch publishes a `test` build, which is how to try out the publish path without touching `latest`.
|
|
43
|
+
|
|
44
|
+
Release branches created before this scheme (`release/v5.2` and earlier) already have patch versions higher than the commit count since their tag.
|
|
45
|
+
To publish a patch from one of them, first tag its tip with the last version published from it, such as `v5.2.11`; later commits are then versioned `5.2.12` and up.
|