v2.1.0

[lgarron]

Release notes:

• Overhaul the build system. The usage is still the same and icon sizing and layout should be compatible, but:
  • Fonts are no longer inlined into the CSS, allowing for loading of the most efficient format available.
  • Exports are now specifed by the package:
    • @cubing/icons/css: the new recommended entry point for CSS.
    • @cubing/icons/ts: data about available icons in TypeScript.

[lgarron]

@jfly: This is the fight between Biome and npm version I mentioned. I think Biome's formatting is better, but npm is the canonical tool for package publication. Not sure what the best option is here.

[jfly]

Gotcha. I'm happy with:

1. Ignoring package.json
2. OR: adding a postversion that formats package.json

[lgarron]

Alright, I'll stick with ignoring.

postversion might be a good start, but there are various reasons tools might rewrite package.json and I don't have a full list anywhere.

[lgarron]

Release plan:

git switch release-v2.1.0
git rebase main

git checkout main
git merge --ff-only release-v2.1.0

# Using: https://github.com/lgarron/dotfiles/blob/b71bea0c5d3a8c310f67145329f807eb2a8d417b/scripts/git/tagpush.ts
tagpush
make publish

[lgarron]

Okay, I shook out a few things in the pre-releases and https://cdn.cubing.net/v0/css/@cubing/icons/css is now working well.

[lgarron]

@jfly, you good with releasing?

(There's a merge conflict, but it just needs a rebase once we know what version we're bumping from.)

[jfly]

Release plan: [...]

uber nit: Can we stick to the documented release process?

[lgarron]

Release plan: [...]

uber nit: Can we stick to the documented release process?

Unfortunately, I actually really disagree with that process, as it:

• Does not put the release notes into git history.
• Does not put release notes into the GitHub release (by the corresponding workflow).
• Diverges from the process used by all the other cubing/@cubing packages.

That said, I would definitely really like to have a re-think of this once we introduce npm publication from GitHub, whether that means something like conventional commits, in-tree release notes, or otherwise.

[lgarron]

From talking to @jfly, I'm actually going to bump this to v3.0.0. The switch to fantasticon was not meant to be a breaking change, but:

1. https://www.hyrumslaw.com/
2. Obligatory XKCD:
   

A full version bump at least avoids anyone who's relying on semantic version to avoid implicit behaviour.

[lgarron]

Published as v3.0.0 instead:

• 9c57cce
• https://github.com/cubing/icons/releases/tag/v3.0.0
• https://www.npmjs.com/package/@cubing/icons/v/3.0.0

[jfly]

That said, I would definitely really like to have a re-think of this once we introduce npm publication from GitHub

Agreed. Let's discuss over in cubing/actions-workflows#3