Skip to content

chore: add 1.6.0 changelog notes #5425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

caseyisonit
Copy link
Contributor

Description

Add in the changelog notes to global changelog for 1.6.0

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (minor updates related to the tooling or maintenance of the repository, does not impact compiled assets)

Checklist

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • If my change required a change to the documentation, I have updated the documentation in this pull request.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have reviewed at the Accessibility Practices for this feature, see: Aria Practices

Best practices

This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against main.

@caseyisonit caseyisonit requested a review from a team as a code owner May 1, 2025 21:19
Copy link

changeset-bot bot commented May 1, 2025

⚠️ No Changeset found

Latest commit: 1c27c30

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

Copy link

github-actions bot commented May 1, 2025

Branch preview

Review the following VRT differences

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

Copy link

github-actions bot commented May 1, 2025

Tachometer results

Currently, no packages are changed by this PR...


- **icons-workflow**: added missing S2 icons

### Bug Fixes
Copy link
Contributor

@Rajdeepc Rajdeepc May 2, 2025

Choose a reason for hiding this comment

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

If we choose to move forward with the changesets approach, I believe it makes sense to keep the default grouping as Major, Minor, and Patch, as it aligns well with semantic versioning and keeps things simple for now.

That said, if we later decide to adopt a more customized grouping—like Bug Fixes, Features, etc.—we’ll likely need to introduce additional customizations to support that structure effectively.

In the meantime, please go ahead and use the script in this PR to start automatically generating the global CHANGELOG. It should help us get closer to a more streamlined and consistent release process.

Let me know if anything feels unclear or if you'd like to explore other options together!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants