Commit 9f146ab
Change CI to publish to GitHub package registry
* Scope the package name by organisation. This ties the package to the
RPF organisation rather than just to my user and means that, for
example, any member of the organisation can publish the package.
* Only publish package on successful builds of the experience-cs
branch.
* Use organisation-specific release version to avoid confusion with
versions in the canonical package and use "experience-cs" string
instead of "raspberrypifoundation" to distinguish it from the package
version(s) used by the Code Club World project.
* Always publish using "latest" npm tag; not "hotfix" or "stable".
* Add `--access public` option to `npm publish` command, because scoped
packages only allow "restricted" access by default.
* We can use the GITHUB_TOKEN that is made available by default in a
GitHub Action as the NODE_AUTH_TOKEN, although we need to add the
`packages: write` permission to the Action.
Co-authored-by: Chris Roos <chris.roos@gofreerange.com>
Co-authored-by: Chris Lowis <chris.lowis@gofreerange.com>1 parent 2848f0e commit 9f146ab
3 files changed
Lines changed: 32534 additions & 32526 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
| 6 | + | |
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
| 17 | + | |
17 | 18 | | |
18 | 19 | | |
19 | 20 | | |
| |||
28 | 29 | | |
29 | 30 | | |
30 | 31 | | |
| 32 | + | |
31 | 33 | | |
32 | 34 | | |
33 | 35 | | |
| |||
79 | 81 | | |
80 | 82 | | |
81 | 83 | | |
82 | | - | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
83 | 90 | | |
84 | | - | |
85 | | - | |
86 | | - | |
| 91 | + | |
87 | 92 | | |
88 | 93 | | |
89 | 94 | | |
| |||
0 commit comments