Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Nov 14, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@leafygreen-ui/[email protected]

Minor Changes

Patch Changes

@leafygreen-ui/[email protected]

Minor Changes

  • c7d6e62: Export Align and Justify enums

Patch Changes

@leafygreen-ui/[email protected]

Minor Changes

Patch Changes

  • 55580b8: The GuideCue is updated for the focus to be on the primary button instead of the close button when opened for an improved UX
  • Updated dependencies [43810b4]

@leafygreen-ui/[email protected]

Minor Changes

  • c7d6e62: Export Align, Justify, and RenderMode enums

Patch Changes

@leafygreen-ui/[email protected]

Minor Changes

Patch Changes

@leafygreen-ui/[email protected]

Minor Changes

  • ec4fad8: Added Tertiary, OnSuccess, and OnError border color variants. Added OnSuccess, OnError, and OnSuccessLink text color variants

@lg-tools/[email protected]

Minor Changes

  • ee58160: - Added new flags to link script to cover broader use cases:
    • --no-parallel: Run the link command sequentially for each package. Useful for when the default parallel approach fails
    • --launch-env: A string of environment variable lines as KEY=VALUE, separated by a newline. Only the specified environment variables will be used during npm link commands in the source and destination directories. This is useful to workaround environment variable pollution by tools such as version managers (e.g., asdf) or script runners (e.g., pnpm) that override the script's environment which impacts the launched npm link commands. We recommend using --launch-env="$(env)" to use your original shell environment.
    • Improve documentation for linking in DEVELOPER.md
  • 999febf: developer experience slightly improves by adding more detailed logging to spawn processes in the link script. Previously, running link script would lead to a group of processes being spawned in parallel all piping their stdout and stderr to the console in verbose mode which made it difficult to distinguish what each line of output was from which process. The command and working directory are also now logged for each process along with their exit code.

Patch Changes

  • 56804b8: Refactored lg and lg-build scripts to share build command registration logic, ensuring consistent options and argument handling which fixes an issue where lg-build tsc was not processing args (e.g. --verbose) correctly. Also removed the unused --direct option from the build commands/scripts.
  • Updated dependencies [ee58160]
  • Updated dependencies [56804b8]
  • Updated dependencies [999febf]

@lg-tools/[email protected]

Minor Changes

  • ee58160: - Added new flags to link script to cover broader use cases:
    • --no-parallel: Run the link command sequentially for each package. Useful for when the default parallel approach fails
    • --launch-env: A string of environment variable lines as KEY=VALUE, separated by a newline. Only the specified environment variables will be used during npm link commands in the source and destination directories. This is useful to workaround environment variable pollution by tools such as version managers (e.g., asdf) or script runners (e.g., pnpm) that override the script's environment which impacts the launched npm link commands. We recommend using --launch-env="$(env)" to use your original shell environment.
    • Improve documentation for linking in DEVELOPER.md
  • 999febf: developer experience slightly improves by adding more detailed logging to spawn processes in the link script. Previously, running link script would lead to a group of processes being spawned in parallel all piping their stdout and stderr to the console in verbose mode which made it difficult to distinguish what each line of output was from which process. The command and working directory are also now logged for each process along with their exit code.

Patch Changes

@leafygreen-ui/[email protected]

Patch Changes

  • 43810b4: Expand post-build script to validate that no unnecessary @emotion packages are imported into icon bundles.

@leafygreen-ui/[email protected]

Patch Changes

  • d816392: Fixes types reference file in package.json. Importing { Spinner } from "@leafygreen-ui/loading-indicator/spinner" should no longer result in TS errors
  • Updated dependencies [ec4fad8]

@lg-tools/[email protected]

Patch Changes

  • 56804b8: Refactored lg and lg-build scripts to share build command registration logic, ensuring consistent options and argument handling which fixes an issue where lg-build tsc was not processing args (e.g. --verbose) correctly. Also removed the unused --direct option from the build commands/scripts.

@github-actions github-actions bot requested a review from a team as a code owner November 14, 2025 00:28
@github-actions github-actions bot requested review from adamrasheed and tsck and removed request for a team November 14, 2025 00:28
@github-actions github-actions bot force-pushed the changeset-release/main branch from 8841eaf to 1f9c13e Compare November 14, 2025 16:17
@github-actions github-actions bot requested a review from a team as a code owner November 14, 2025 16:17
@github-actions github-actions bot requested review from shaneeza and stephl3 and removed request for a team November 14, 2025 16:17
@github-actions github-actions bot force-pushed the changeset-release/main branch 7 times, most recently from 2dca155 to 0c665d2 Compare November 20, 2025 22:10
@github-actions github-actions bot force-pushed the changeset-release/main branch from 0c665d2 to 79d7376 Compare November 20, 2025 22:14
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.

2 participants