Skip to content

Adjust release process to be based on package.json version#75

Open
Ikuni17 wants to merge 9 commits intoelastic:masterfrom
Ikuni17:fix/release-process-changes
Open

Adjust release process to be based on package.json version#75
Ikuni17 wants to merge 9 commits intoelastic:masterfrom
Ikuni17:fix/release-process-changes

Conversation

@Ikuni17
Copy link
Copy Markdown
Contributor

@Ikuni17 Ikuni17 commented Mar 25, 2026

The main purpose of this is to get an automated release process in place for when #65 is ready.

  • Moves release from dispatched manual workflow, to triggered by package.json version bump. Effectively making the package.json version the source of truth.
  • The publish-release workflow gates on package.json changes in master and detects when the version has actually changed.
  • Version bumps are expected to come in through base repo PRs with a branch in the form release/**. Once the PR is merged the automated release process fires off.
  • update-dist workflow runs on every push to master to keep the dist in sync with source code. This creates a race condition when the version bump is merged. The workflow was adjusted to also detect the version bump PR, and push commits to it. This becomes a required check and ensures the release always has the proper dist. Additionally this repo requires up to date branches to merge in the event the release PR gets behind.
  • Adds .github/release.yml and corresponding labels to categorize automatically generated release notes.

@Ikuni17 Ikuni17 self-assigned this Mar 25, 2026
@Ikuni17 Ikuni17 requested a review from Copilot March 26, 2026 00:38
@Ikuni17 Ikuni17 marked this pull request as ready for review March 26, 2026 00:39
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository’s release process so that releases are derived from the root package.json version, with release notes generated automatically and categorized via GitHub’s release config.

Changes:

  • Switch from a manually-dispatched release workflow to an automatic “publish on version bump” workflow.
  • Document the new release process in the README and add a minimal CHANGELOG.md pointing to GitHub Releases.
  • Add .github/release.yml to configure autogenerated release notes categories.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
package.json Sets the root package version used as the release source of truth.
README.md Updates release documentation to reflect version-driven releases and autogenerated notes.
CHANGELOG.md Adds a lightweight changelog stub directing readers to GitHub Releases.
.github/workflows/release.yml Removes the previous manually-triggered release workflow.
.github/workflows/publish-release.yml Adds an automated release workflow that tags/releases based on package.json version.
.github/release.yml Defines label-based categories/exclusions for autogenerated GitHub release notes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Ikuni17 and others added 2 commits March 25, 2026 22:49
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@Ikuni17 Ikuni17 added the skip-for-release-notes Exclude from auto-generated release notes when publishing the next release. label Mar 27, 2026
{
"name": "elastic-github-actions",
"version": "3.0.0",
"version": "2.1.1",
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a revert to align with the previous release to stop an automated release from happening post merge of this PR.

@Ikuni17 Ikuni17 requested a review from a team March 28, 2026 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-for-release-notes Exclude from auto-generated release notes when publishing the next release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants