Skip to content

Create a changeset file per package on framework bump#5031

Merged
dskloetc merged 1 commit into
mainfrom
kloet/per-ea-framework-bump
Jun 8, 2026
Merged

Create a changeset file per package on framework bump#5031
dskloetc merged 1 commit into
mainfrom
kloet/per-ea-framework-bump

Conversation

@dskloetc

@dskloetc dskloetc commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Description

Currently the packages/scripts/src/framework/version-bump.sh script creates a single changeset file for all the packages.
This means that we have to release all those packages at the same time.
But creating a separate changeset file per package we can release individual packages when we want.

Changes

  1. Create changeset file names with a single call to yarn node to avoid the script being very slow.
  2. Generate a changeset file per changed package.
  3. Run with /usr/bin/env bash instead of /bin/bash as mapfile requires bash 4+ and Mac installs version 3 in /bin/.

Steps to Test

Created #5030

Quality Assurance

  • If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant infra-k8s configuration file.
  • If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant adapter-secrets configuration file.
  • If a new adapter was made, or a new endpoint was added, update the test-payload.json file with relevant requests.
  • The branch naming follows git flow (feature/x, chore/x, release/x, hotfix/x, fix/x) or is created from Jira.
  • This is related to a maximum of one Jira story or GitHub issue.
  • Types are safe (avoid TypeScript/TSLint features like any and disable, instead use more specific types).
  • All code changes have 100% unit and integration test coverage. If testing is not applicable or too difficult to justify doing, the reasoning should be documented explicitly in the PR.

@changeset-bot

changeset-bot Bot commented Jun 8, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7496de6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dskloetc dskloetc force-pushed the kloet/per-ea-framework-bump branch from 74da5ac to 7496de6 Compare June 8, 2026 13:07
@dskloetc dskloetc marked this pull request as ready for review June 8, 2026 13:07
@dskloetc dskloetc requested review from a team and Copilot June 8, 2026 13:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@dskloetc dskloetc enabled auto-merge (squash) June 8, 2026 13:10
@dskloetc dskloetc merged commit 8c0797f into main Jun 8, 2026
20 of 22 checks passed
@dskloetc dskloetc deleted the kloet/per-ea-framework-bump branch June 8, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants