Repository navigation
Release 0.13.0? #382
Description
Activity
- addedtype: questionRequest for information or clarification. Not an issue.Request for information or clarification. Not an issue.
on Feb 5, 2015 👍
Will wait for #381 then we can 🚢
Gonna wait some more for #379 which might introduce breaking changes and this is priority for getting the build working smoothly again.
How do we release anyway? @silvolu might hold the key.
We just
npm version __major|minor|patch__and push it to github.Oh does @selfiebot see the tag and handle it? It's been so long since a release I forget.
Yep, @selfiebot is king of npm publish and doc building.
@selfiebot appears to be dead because our docs are not building. Could someone please investigate?
And teach me how to do it if possible? :)
I believe we discovered selfie wasn't happy with our failing tests, so it aborted before building the docs. After #402, hopefully the flakiness will be eradicated.
Not fixed, but too many issues for the same thing :$ Specific issue and discussion for solution: #411
20 remaining items
- added a commit that references this issue
on Feb 3, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 17, 2026 - added a commit that references this issue
on Feb 23, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 18, 2026

We haven't shipped since before Christmas despite numerous changes. I propose we ship
0.13.0sometime soon. I'd suggest we skip0.13.0for superstition but semver might be sad about that.