Skip to content

Releases: nolsen311/Pfsense-REST

v0.10.2

v0.10.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 06 Sep 20:10
4cf1822

What's Changed

Full Changelog: v0.10.1...v0.10.2

v0.10.1

Choose a tag to compare

@github-actions github-actions released this 06 Sep 19:20
82f44db

Changes

Full changelog: v0.10.0...v0.10.1

Massive fixes!

Choose a tag to compare

@nolsen311 nolsen311 released this 06 Sep 18:32
95b67c9

v0.10.0

First release with correct version metadata — the tag, manifest.json, and
shipped code now all report the same version. If you're on "0.9.1" your
integration was reporting 0.9.0 due to a release-tooling bug; 0.10.0 fixes that.

  • New option: "Reset matching states when a rule switch is toggled"
    (Settings → Devices & Services → pfSense REST → Configure). Off by default.
  • Fix a poll failure ("cannot use 'dict' as a set element") from the
    default-gateway response.
  • Work around the REST API rejecting a rule toggle with
    FIELD_EMPTY_NOT_ALLOWED when a rule's state type was left blank.
  • Adopt the Home Assistant ruff lint/format standard across the codebase
    (no runtime behaviour change).

If HACS recorded a 2.x/3.x version for a very old install, it will not offer
this as an update — remove the integration in HACS and re-download.

Fixing a LOT of stupid shit

Choose a tag to compare

@nolsen311 nolsen311 released this 06 Sep 17:30
d397ef4

What's Changed

#What's actually in v0.9.3
I checked the v0.9.1 tree — all the code fixes already shipped in v0.9.1: the gateway poll-crash fix, the statetype PATCH workaround, and the "reset matching states on toggle" option are all there. What v0.9.1 got wrong is its manifest — it says 0.9.0 (the lag bug), so anyone on v0.9.1 has an integration that misreports its own version.

So v0.9.3 is a metadata-correcting release:

First release where tag == manifest == shipped content (0.9.3 everywhere).
CI fixes: Code Checker checks out a real branch; release.yml no longer rewrites the manifest post-tag and now fails a release whose tag ≠ manifest.
Gives everyone on 0.9.0/0.9.1 a clean update that finally reports the right version.
No new user-facing fix beyond v0.9.1 — there are none pending.

The lag fix
release.yml before: bump manifest.json from the tag name after publish → tag ships the old version. Now: manifest.json is bumped in-repo (done — it's 0.9.3 on this branch), and release.yml just verifies the tag matches, builds the zip, uploads it. Nothing edits the manifest at release time.

Full Changelog: v0.9.1...v0.9.3

Kill States & other stupid shit.

Choose a tag to compare

@nolsen311 nolsen311 released this 06 Sep 17:01
7fb2ba2

What's Changed

Full Changelog: v0.9.0...v0.9.1

Is it Working yet?

Choose a tag to compare

@nolsen311 nolsen311 released this 06 Sep 15:59
b59e5fb

What's Changed

New Contributors

Full Changelog: https://github.com/nolsen311/Pfsense-REST/commits/v0.9.0