Blake Matthes
b18d1ced6d
All checks were successful
Build and Push LST Docker Image / docker (push) Successful in 1m54s
113 lines
1.9 KiB
Markdown
113 lines
1.9 KiB
Markdown
|
|
|
|
docker build -t git.tuffraid.net/cowch/lst_v3:latest .
|
|
docker push git.tuffraid.net/cowch/lst_v3:latest
|
|
|
|
docker compose pull && docker compose up -d --force-recreate
|
|
|
|
How to choose the bump
|
|
|
|
Use this rule:
|
|
|
|
patch = bug fix, small safe improvement
|
|
minor = new feature, backward compatible
|
|
major = breaking change
|
|
|
|
Changesets uses semver bump ty
|
|
|
|
|
|
### daily process
|
|
npm commit
|
|
|
|
- when closing a issue at the end add
|
|
Use one of these in the commit body or PR description:
|
|
|
|
- - Closes #123
|
|
- - Fixes #123
|
|
- - Resolves #123
|
|
|
|
Common ones:
|
|
|
|
- - Closes #123
|
|
- - Fixes #123
|
|
- - Resolves #123
|
|
Reference an issue without closing it
|
|
|
|
Use:
|
|
|
|
- - Refs #123
|
|
- - Related to #123
|
|
- - See #123
|
|
|
|
Good safe one:
|
|
|
|
- - Refs #123
|
|
Good example commit
|
|
|
|
Subject:
|
|
|
|
- - fix(cors): normalize external url origin
|
|
|
|
Body:
|
|
|
|
- - Refs #42
|
|
|
|
Or if this should close it:
|
|
|
|
- - Closes #42
|
|
|
|
# Release flow
|
|
npm run changeset:add
|
|
|
|
Pick one:
|
|
|
|
- patch = bug fix
|
|
- minor = new feature, non-breaking
|
|
- major = breaking change
|
|
|
|
Edit the generated .md file in .changeset it will be randomly named and add anything else in here from all the commits that are new to this release
|
|
|
|
Recommended release command
|
|
npm run changeset:version
|
|
|
|
stage the change log file
|
|
|
|
git commit -m "chore(release): version packages"
|
|
|
|
git tag v1.0.1 this will be the new version
|
|
|
|
then push it
|
|
|
|
git push
|
|
git push --tags
|
|
|
|
|
|
|
|
|
|
### release type
|
|
|
|
when we want to go from alpha to normal well do
|
|
npx changeset pre enter alpha
|
|
npx changeset pre enter rc
|
|
|
|
go to full production
|
|
npx changeset pre exit
|
|
npx changeset version
|
|
|
|
### Steps will make it cleaner later
|
|
Daily work
|
|
1. Stage files
|
|
2. npm run commit
|
|
3. Add issue keyword if needed
|
|
4. git push when ready
|
|
|
|
Release flow
|
|
1. npx changeset
|
|
2. pick patch/minor/major
|
|
3. edit the generated md file with better notes
|
|
4. npx changeset version
|
|
5. git add .
|
|
6. git commit -m "chore(release): version packages"
|
|
7. git tag vX.X.X
|
|
8. git push
|
|
9. git push --tags |