feat(ci): enable GitHub Releases and prepare v1.1.0 #28
Conversation
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
Add GitHub Releases creation to release workflow: - Set createGithubReleases: true for automatic release creation - Add fetch-depth: 0 to fetch full git history for proper changelogs - Keep simple push-to-main trigger (branch protection ensures quality) When packages are published, GitHub Releases will be created with: - Version tags (e.g., @lytics/experience-editor@1.1.0) - Changelog content as release notes - Links to published npm packages
Add changeset documenting features since v1.0.1: - Default field values support - Content ranking for recommendations - Date range display conditions - Code quality improvements with Biome
prosdev
added a commit
that referenced
this pull request
Nov 8, 2025
Fixes the release workflow - changesets needs to create `chore:` commits but commitlint was blocking them. Adds `chore` to allowed commit types in commitlint config. Related to #28
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Overview
Enable automatic GitHub Release creation and prepare the first release (v1.1.0) with changesets.
Changes
createGithubReleases: trueto release workflowfetch-depth: 0for proper changelog generationWhat Happens After Merge
@lytics/experience-editorto v1.1.0v1.1.0 Changelog
Before Merging
Ensure NPM Trusted Publishing and GitHub
productionenvironment are configured (see .github/CI.md).