chore(deps): update @atlaskit/heading to v7 - #3316
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for atlassify canceled.
|
|
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
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.



This PR contains the following updates:
6.2.3→7.0.0Release Notes
atlassian/atlassian-frontend-mirror (@atlaskit/heading)
v7.0.0Major Changes
7170acd7feb77-Apply Volt entry-point and multi-export standards via
volt-migrate-package. This is a majorchange to
@atlaskit/heading: the packageexportsmap has been restructured so every publicsubpath now resolves directly to its
./src/*implementation instead of going through anintermediate
./src/entry-points/*re-export. It also introduces new public subpaths:@atlaskit/heading/src/heading-context,@atlaskit/heading/use-heading.Why this is breaking
Because each subpath now points straight at its implementation module, a subpath and the package
root can resolve to the same module instance. Consumers that deep-import the internal
entry-points/*files, or thatjest.mock()a specific subpath, may observe changedresolution/behaviour and need updating.
Migration — public imports are unchanged
Importing the published subpaths (or the package root) continues to work as before:
If you were reaching into the internal entry-point modules, switch to the public subpath:
Before / after
exportsmap"exports": { ".": "./src/index.tsx", - "./heading": "./src/entry-points/heading.tsx", + "./heading": "./src/heading.tsx", "./heading-context": "./src/entry-points/heading-context.tsx", + "./src/heading-context": "./src/heading-context.tsx", + "./use-heading": "./src/use-heading.tsx", }Patch Changes
Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.