Skip to content

Releases: yokomohoyo/insomnium

0.3.0-rc.20

Choose a tag to compare

@yokomohoyo yokomohoyo released this 01 Oct 15:57
7c606dd

What's Changed

Full Changelog: 0.3.0-rc.19...0.3.0-rc.20

0.3.0-rc.19

Choose a tag to compare

@yokomohoyo yokomohoyo released this 01 Oct 05:02
2757d6d

What's Changed

Full Changelog: 0.3.0-rc.18...0.3.0-rc.19

0.3.0-rc.18

Choose a tag to compare

@yokomohoyo yokomohoyo released this 25 Sep 20:50
b59c0c9

What's Changed

Full Changelog: 0.3.0-rc.17...0.3.0-rc.18

0.3.0-rc.17

Choose a tag to compare

@yokomohoyo yokomohoyo released this 25 Sep 20:29
6fbc79e

What's Changed

Full Changelog: 0.3.0-rc.16...0.3.0-rc.17

0.3.0-rc.16

Choose a tag to compare

@yokomohoyo yokomohoyo released this 24 Sep 04:54
4f0e496

What's Changed

Full Changelog: 0.3.0-rc.15...0.3.0-rc.16

0.3.0-rc.15

Choose a tag to compare

@yokomohoyo yokomohoyo released this 24 Sep 02:28
ce5856e

What's Changed

Full Changelog: 0.3.0-rc.14...0.3.0-rc.15

0.3.0-rc.14

Choose a tag to compare

@yokomohoyo yokomohoyo released this 24 Sep 01:43
5133e2b

What's Changed

Full Changelog: 0.3.0-rc.13...0.3.0-rc.14

0.3.0-rc.13

Choose a tag to compare

@yokomohoyo yokomohoyo released this 23 Sep 19:21
d650976

What's Changed

Full Changelog: 0.3.0-rc.12...0.3.0-rc.13

0.3.0-rc.12

Choose a tag to compare

@yokomohoyo yokomohoyo released this 23 Sep 16:47
04fb18a

What's Changed

Full Changelog: 0.3.0-rc.11...0.3.0-rc.12

0.3.0-rc.11

Choose a tag to compare

@yokomohoyo yokomohoyo released this 01 Sep 17:36
708f80c

This is an infrastructure verification release. There are no application changes since 0.3.0-rc.10 — if you are already on rc.10, there is nothing here for you.

It exists to prove a fix to the release pipeline that could only be tested by cutting a real release. Binaries are byte-for-byte equivalent in behaviour to rc.10; the version number is the only functional difference.

Why this release exists

The workflow that publishes the APT repository had never once succeeded on its own. It was triggered by release: published, which runs in the tag's context, while the github-pages environment only permits deployments from main. Every release failed within about a second, before a single step ran:

Tag "0.3.0-rc.10" is not allowed to deploy to github-pages due to
environment protection rules.

Every previous release therefore needed a manual gh workflow run apt-repo.yml --ref main afterwards, and left a failed check on the release regardless.

#85 changed the trigger to workflow_run on the artifact build, which runs in the default branch's context. That also removed a second, quieter bug: the old trigger fired concurrently with the build, so the workflow went looking for a .deb that had not finished uploading.

Neither fix could be verified without publishing an actual release, hence rc.11.

Result: this release completed with no manual intervention. APT Repository started on its own and succeeded, having pooled this release's .deb first — confirming both the environment fix and the race fix.

For Debian/Ubuntu users

apt upgrade now sees 0.3.0~rc.11. The upgrade path is working as intended — which is the substance of what this release verifies.

What's Changed

Full Changelog: 0.3.0-rc.10...0.3.0-rc.11


Looking for the security fixes?

They are in 0.3.0-rc.10, which cleared 1 critical, 12 high and 11 moderate advisories — xmldom, js-yaml, js-cookie, serialize-javascript, protobufjs, @hono/node-server, xml2js, and react-router 6 → 7. Anything at rc.9 or earlier should upgrade for those.