🚀 feat: implement automated release management with Changesets#1512
Merged
Conversation
- Add @changesets/cli for automated versioning - Add @changesets/changelog-github for rich GitHub integration - Install dependencies for enhanced release workflow 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Initialize Changesets configuration with GitHub changelog integration - Set access to public for NPM publishing - Configure repo: aligent/cdk-constructs for proper PR/commit linking - Add Changesets README with usage instructions 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Remove old manual tag-based release workflow - Add new Changesets-powered release workflow - Enable automatic GitHub releases with generated changelogs - Add proper permissions and git configuration - Support both main and feature branch releases - Include comprehensive testing before publishing 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Create automated changeset validation for pull requests - Use Nx affected detection for accurate package identification - Map Nx project names to publishable package names - Add intelligent PR comments showing affected packages - Validate changeset coverage for all affected packages - Include helpful commands and tips in PR comments - Auto-update comments when changesets are added/removed 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Add Nx affected detection to developer workflow - Include yarn affected:packages command for accurate package detection - Update release process documentation for Changesets automation - Add guidance on using Nx dependency graph analysis - Document new workflow: check affected packages → create changesets - Add pro tips for accurate changeset creation 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- graphql-mesh-server: 0.0.1 → 3.1.1 - cloudfront-security-headers: 2.0.0 → 0.4.0 - header-change-detection: (missing) → 1.6.1 - feature-env-handlers: 2.0.1 → 2.1.0 - prerender-fargate: 2.5.1 → 2.11.0 - prerender-proxy: 2.1.4 → 2.4.2 - geoip-redirect: 0.1.0 → 1.1.1 - static-hosting: 2.7.2 → 2.8.2 - basic-auth: 2.0.0 → 0.2.1 - shared-vpc: 2.0.0 → 0.2.0 - rabbitmq: 2.0.0 → 0.2.0 - esbuild: 2.3.0 → 2.4.1 - waf: 2.2.0 → 2.3.0 All local package.json versions now match their NPM published versions exactly. 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Check for any changeset files before requiring affected packages - This handles cases where infrastructure changes include changesets - Resolves issue where pipeline incorrectly reported no changeset
Contributor
|
✅ Changeset detected - Thanks for adding release notes! |
- Remove hardcoded CDK construct package list from changeset-check workflow - Update npm affected:packages script to use dynamic discovery - Use find command to discover all packages in /packages/ directory - Automatically handles new packages without code changes - Fixes issue with non-existent 'prerender-alpine' package in hardcoded list - Discovered 13 actual packages vs 14 in hardcoded list
daniel-vdp
force-pushed
the
feature/release-management-with-changesets
branch
from
71560d5 to
fbe3590
Compare
daniel-vdp
requested review from
AdamJHall,
aaronmedina-dev,
hubertott and
porhkz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Summary
This PR introduces automated release management using Changesets, replacing our manual release workflow with a more streamlined, developer-friendly approach! 🎉
🔄 What's Changed
✨ New Features
🛠️ Workflow Updates
mainbranch🔒 Security Improvements
changesets/actionto commit hashe0145ed(v1.5.3) for enhanced security📚 Documentation
CONTRIBUTING.mdwith comprehensive Changesets workflow guide🧪 Testing
The new workflows have been configured to:
🎪 How It Works
Developer creates a changeset 🎨
PR validation ensures changeset exists 👀
On merge to main 🚢
🏃♂️ Migration Notes
📋 Checklist