Repository navigation
Releases: TechProofing/ci-releases
Releases · TechProofing/ci-releases
Release list
v1.0.6
🚀 Initial Commit
- Initial project setup with Node.js v22.3.0, Vite, React, and TypeScript.
- Vite seems to want a new version of node past 18 to use their new version.
- Project structure created.
- Basic dependencies installed and configured.
🛠️ Setting Up CI
- GitHub Actions workflows created for deployment and release.
- Deploy Workflow (
deploy.yml):- Automatic deployment on push to
main,staging, andrelease/**branches. - Uses
actions/checkout@v2for repository checkout. - Configures Node.js environment with
actions/setup-node@v2. - Runs tests and builds the project.
- Pushes changes with tags using
GITHUB_TOKEN.
- Automatic deployment on push to
📦 Versioning
- Project versioning handled using
lerna. - Version Update Script (
./script/next_version.sh):- Determines the next version based on the current state of the repository.
- Differentiates between main and other branches.
- Update Package Versions:
- Runs
lerna versionto update package versions without pushing changes immediately.
- Runs
📝 Update CHANGELOG
- Automated updating of the
CHANGELOG.mdfile with the current date. - Update CHANGELOG Step:
- Uses the
sedcommand to replace the placeholder date with the current date. - Commits the updated
CHANGELOG.mdto the repository.
- Uses the
📢 Release
- Automated release creation using a custom script.
- Make GitHub Release:
- Creates a GitHub release with the latest changelog.
- Uses
GITHUB_TOKENfor authentication. - Integrates with the custom release script
make-github-release.js.
[v0.1.0] - 2024-06-15
🎉 Initial Setup
- Project repository initialized.
- Initial commit with basic project structure and dependencies.
How to Use
Making a Commit
git add .
git commit -m "Your commit message"
git push origin your-branch