Hey Bootstrap community!

We know things have felt a bit quiet lately. That’s mainly because the core team works on Bootstrap in their spare time—and sometimes, that time just isn’t there. But despite that, we’ve made meaningful progress, especially on Sass compatibility issues.

✅ v5.3.4: Sass Deprecation Warning Fixes

One of the main updates in Bootstrap v5.3.4 (and the quick follow-up v5.3.5) was to resolve the Sass deprecation warnings introduced in Sass v1.77.7.

We’ve patched our code to prevent these warnings from showing up when using Sass versions up to 1.78.0. If you stay on that version or below, you shouldn’t see any deprecation warnings.

📝 Note: Sass deprecated several features starting in 1.77.x. They will become breaking in Sass v2.

🔧 If You're Still Seeing Warnings...

If you’re compiling Bootstrap Sass and seeing deprecation warnings, here are your options:

• Pin your Sass version to 1.78.0, the latest version without issues for Bootstrap (as of now).
• Silence the warnings if your build system allows it.
• Ignore them for now—these are just warnings, and the deprecated features are still functional.
• Check out these issues for workarounds or discussion:
  • SASS deprecation warnings with version 1.77.7 - Mixed declarations #40621
  • New deprecations in Sass 1.79 #40849
  • dart-sass 1.80.0+ throwing a lot of deprecations #40962

It's not released yet, but our documentation, from v5.3.6, will temporarily include solutions for tools like Parcel, Webpack, and Vite in our 'next' documentation, or directly in our Bootstrap examples:

• Parcel starter
• Vite starter
• Vue starter
• Webpack starter

🧨 Sass 1.79.x Introduced a Breaking Change

Starting with Sass 1.79.x, things get trickier: the red(), green(), and blue() functions were deprecated in favor of color.channel(). Unfortunately:

• color.channel() isn’t supported by Node Sass
• There’s no workaround for this on our side

This means: to fix these and other Sass deprecation issues coming from 1.80+, we have to drop Node Sass support.

🪄 Step 1: Moving Docs from Hugo to Astro

Our documentation currently uses Hugo, which depends by default on Node Sass. That’s a blocker.

We’re migrating to Astro, which fully supports Dart Sass (and for other reasons as well):

🔧 PR in progress: #41251

This will be released in v5.3.6 (or another v5.3.x), a patch release, since it doesn't impact how Bootstrap works—just the way we build and ship the docs.

This is our primary focus at the time of writing.

Once that’s done, we'll fix bugs quickly in follow-ups like v5.3.7, v5.3.8, etc. Community help testing this will be hugely appreciated! 🙏

✨ v5.4.0: Final Feature Release

After the docs work wraps up, we’ll ship v5.4.0, the last Bootstrap 5 release with new features.

Many of the PRs for this have already been reviewed and are ready to merge. We still need to go through a triage phase for the v5.4.0 GitHub project, but the goal is to keep that process lightweight and not spend too much time on it.

🔥 v5.5.0: Dropping Node Sass & Switching to Sass Modules

After v5.4, we’ll ship v5.5.0, which will:

• Drop Node Sass support completely
• Refactor our Sass code to use the Sass module system (@use, @forward)
• Clean up all remaining deprecation warnings

This will be a breaking change for Sass users, but it’s necessary for long-term compatibility.

Sass users will need to:

• Use @use instead of @import
• Explicitly load modules like @use "sass:color", @use "sass:math"
• And maybe other stuff not yet identifeid

That’s a big change that needs to happen really soon, but we believe it’s manageable with clear communication.

Why not call this v6? Because it doesn’t change how Bootstrap is used, only how it’s compiled. We think v6 should represent a bigger conceptual shift. Like a new epoch.

🔭 Looking Ahead: Bootstrap v6

We have started the development of Bootstrap v6, and we want it to be more than just a technical update—it should reflect a new philosophy or vision for Bootstrap.

That’s why:

• Dropping Node Sass and switching to modules is not v6 material on its own
• v6 will introduce broader changes, possibly even new paradigms
• We’re studying the Epoch Semantic Versioning, where major versions could be a combination between new epochs that mark conceptual shifts (what we used to call v5, v6, etc.), and breaking changes like regular Semver. An implementation could be something as described as in the Epoch Semantic Versioning - by Anthony Fu 🤷

TL;DR – Bootstrap Release Roadmap