AndreiandLukas Stracke
46899dbf22
* feat(sourcemaps): Add `inject` option to inject debug ids into sourcefiles and sourcemaps * Update README with whats-new section * Add `inject` example to README * Update README.md Co-authored-by: Lukas Stracke <[email protected]> --------- Co-authored-by: Lukas Stracke <[email protected]>
1.6 KiB
Publishing a release
The build.yml workflow will build a Docker image every time a pull request merges to master and upload it to the GitHub registry.
Warning
Merging pull requests into
mastermeans changes are live for anyone who uses the action regardless of bumping the version. Be extremely careful and intentional with changes and ensure properly testing them before merging, see #Testing for more info.
Note
Unfortunately, we only use the
latesttag for the Docker image, thus, making use of a version with the action ineffective (e.g.v1vsv1.3.0). See #129 on how to fix this.
Note
At the moment our Docker image publishing is decoupled from
tagcreation in the repository. We should only publish a specific Docker tag when we create a tag (you can make GitHub workflows listen to this). See #102 for details. Once this is fixed, merges tomasterwill not make the Docker image live.
When you are ready to make a release, open a new release checklist issue and follow the steps in there.
Note
At the moment releases are only used to inform users of changes.
The Docker build is multi-staged in order to make the final image used by the action as small as possible to reduce network transfer (use docker images to see the sizes of the images).