Skip to content

Release v5.3.7 #41509

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 10, 2025
Merged

Release v5.3.7 #41509

merged 1 commit into from
Jun 10, 2025

Conversation

julien-deramond
Copy link
Member

@julien-deramond julien-deramond commented May 31, 2025 •
edited
Loading

Warning

Only one remaining issue in v5.3.7 may be challenging to resolve. We need to decide whether it's a must-fix for the v5.3.7 release.

This PR releases v5.3.7.

The release was built using the following commands:

  • npm run release-version 5.3.6 5.3.7
  • npm run release

Possible Items for a Blog Post or Release Note

/cc @mdo

📚 Documentation

  • Fixed broken "View on GitHub" URLs
  • Corrected HTML <head> content generated by the "Download examples" button
  • Refined sanitizer documentation for clarity and completeness
  • Improved accessibility in the "On this page" table of contents and section heading anchor links
  • Relocated ads to the right sidebar to minimize content reflow
  • Added a new section on the Download page for the Intelissence extension
  • Clarified the "Via JavaScript" usage example for Accordion Collapse
  • Made internal documentation improvements to support future maintenance (no visible user impact)
  • Mention CDN integrity and crossorigin attributes in introduction page
  • Enhance floating labels placeholder usage description
  • Add example of showing dynamic range value with output

🎨 Sass

  • Consolidated multiple 'none' values in the box-shadow Sass mixin for cleaner output

🤖 JavaScript

  • Fixed popover and tooltip behavior with a trigger: "hover click" configuration

🤝 Contributions

  • Added recommended VSCode extensions and settings configuration to the repository

@github-project-automation github-project-automation bot moved this to To do in v5.3.7 May 31, 2025
@julien-deramond julien-deramond moved this from To do to In progress in v5.3.7 May 31, 2025
@julien-deramond julien-deramond force-pushed the v537 branch 6 times, most recently from 18d56e0 to c0cb264 Compare June 9, 2025 12:20
@mdo mdo marked this pull request as ready for review June 10, 2025 15:43
@mdo mdo requested review from a team as code owners June 10, 2025 15:43
mdo
mdo approved these changes Jun 10, 2025
View reviewed changes
Copy link
Member

@mdo mdo left a comment

Choose a reason for hiding this comment

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

Thank you!!!

@mdo mdo merged commit e0032ae into main Jun 10, 2025
14 checks passed
@mdo mdo deleted the v537 branch June 10, 2025 15:44
@github-project-automation github-project-automation bot moved this from In progress to Done in v5.3.7 Jun 10, 2025
@Spixmaster
Copy link

Spixmaster commented Jun 17, 2025 •
edited
Loading

I think you forgot to tag the version and publish to npm.

@julien-deramond
Copy link
Member Author

I think you forgot to tag the version and publish to npm.

We didn't forget! We just haven't had time to wrap up the release. It'll be ready soon :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mdo mdo mdo approved these changes

Assignees
No one assigned
Labels
release v5
Projects
No open projects
v5.3.7
Status: Done
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@julien-deramond @Spixmaster @mdo