Skip to content
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.

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

Release/21.0.0-alpha.1 #2230

Merged
merged 2 commits into from
Feb 26, 2025
Merged

Release/21.0.0-alpha.1 #2230

merged 2 commits into from
Feb 26, 2025

Conversation

steveblue
Copy link
Contributor

@steveblue steveblue commented Feb 21, 2025

What kind of change does this PR introduce? (check one with "x")

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

What is the current behavior? (You can also link to an open issue here)

Release build was not publishing assets.

What is the new behavior?

Release build works as intended. Built from fresh install and needed to reinstall sass to get library build to output properly. Cross-reference with legacy build and all looks as intended. We now incur the same warnings as in other repos about @import so we should fix those in another release. I also cleaned up stray tags from the fork so this release could be tagged properly.

Does this PR introduce a breaking change? (check one with "x")

  • Yes
  • No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

@steveblue steveblue changed the title Release/21.0.0 alpha.1 Release/21.0.0-alpha.1 Feb 21, 2025
@steveblue steveblue merged commit 0f6792a into master Feb 26, 2025
3 checks passed
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.

3 participants