Version Packages

[hashibot-hds]

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

@hashicorp/[email protected]

Minor Changes

CodeBlock - Added height toggle control, which is present when a maxHeight is set and code content height exceeds the maxHeight value

#2826

breakpoints - Added responsive breakpoint values and helpers for responsiveness

#2848

Pagination - Replaced custom breakpoint (1000px) with standard lg (1088px) breakpoint

Stepper::Nav - Replaced custom breakpoint (550px) with standard sm (480px) breakpoint

AppHeader - Removed usage of --hds-app-desktop-breakpoint CSS variable and relied on the @breakpoint argument for override of mobile behavior

AppSideNav - Removed usage of --hds-app-desktop-breakpoint CSS variable, added @breakpoint argument, and relied on it for override of mobile behavior

#2859

Patch Changes

AppHeader - Fixed import path for hds-breakpoints

AppSideNav - Fixed import path for hds-breakpoints

#2886 - Thanks @aklkv for the contribution! 🙏

AppSideNav - Fixed bug where scrolling was blocked when the AppSideNav was expanded on desktop views. Also fixed bug which allowed user to focus links that were visually hidden.

#2869

Time - Fixed type error where the TooltipButton text could be undefined.

#2877

AppSideNav - Fixed component types for AppSideNav::Portal and AppSideNav::Portal::Target to no longer require @target or @name.

SideNav - Fixed component types for SideNav::Portal and SideNav::Portal::Target to no longer require @target or @name.

#2908

Form::Label - Forced the for HTML attribute to be converted to a string

#2863

AdvancedTable - Added @maxHeight argument, which sets the max height of the Advanced Table and automatically adds a sticky header to it. Also updated the container styles to constrain the Advanced Table width to the parent's width.

#2865

CodeBlock - Fixed issues with line numbers when line wrapping is present and when the number of lines changes dynamically; line highlighting when the Code Block is hidden from view initially such as when used inside a Tabs component; and line highlighting when hasLineNumbers is false.

#2856

Modal - Fixed bug with click event listener not properly removed

#2902

Stepper::Nav - Fixed issue in Safari with text alignment on interactive steps

#2909

CodeBlock - Added arguments @ariaLabel, @ariaLabelledBy, and @ariaDescribedBy. Added screen-reader only copy for highlighted lines.

hds-clipboard - Prevent screen-reader only text (text with the sr-only class) from being copied to the clipboard.

#2879

Introduce the hds-resolve-link-to-component utility to correctly resolve the LinkTo component when @isRouteExternal is set on HdsBreadcrumbItem or HdsInteractive. Consumers are now required to install ember-engines when @isRouteExternal is true.

#2867 - Thanks @aklkv for the contribution! 🙏

Layout::Flex - Added missing export of component/subcomponent

Layout::Grid - Added missing export of component/subcomponent

#2883

🔄 Updated dependencies:

• @hashicorp/[email protected]

@hashicorp/[email protected]

Minor Changes

start, end, and text-wrap icons added. Fixed the vertical alignment of top and bottom.

#2917

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
hds-showcase	✅ Ready (Inspect)	Visit Preview	Jun 5, 2025 1:46pm
hds-website	✅ Ready (Inspect)	Visit Preview	Jun 5, 2025 1:46pm

[alex-ju]

I don't see any component changelog entries – do you plan to add those manually in a separate PR? We also seem to be missing the documentation link for this version.

[didoo]

I don't see any component changelog entries – do you plan to add those manually in a separate PR? We also seem to be missing the documentation link for this version.

@alex-ju you're right, I forgot they were undone by the recent merge to main. What do you think of trying as en experiment to merge this as is, and open a quick follow-up PR with the expected changes? In this way we can validate the idea that the two operations could be disjointed to avoid this kind of issues. Thought?

[alex-ju]

I don't see any component changelog entries – do you plan to add those manually in a separate PR? We also seem to be missing the documentation link for this version.

@alex-ju you're right, I forgot they were undone by the recent merge to main. What do you think of trying as en experiment to merge this as is, and open a quick follow-up PR with the expected changes? In this way we can validate the idea that the two operations could be disjointed to avoid this kind of issues. Thought?

Happy to experiment if you find it valuable

[didoo]

@alex-ju @dchyun since we have agreed to merge this PR as is, and do the release notes in a quick separate follow-up PR, can I get an approval?

[didoo]

Follow-up PR: #2933