chore(release): keep semantic-release on 0.x series and revert version to 0.148.0 by bdraco · Pull Request #1674 · python-zeroconf/python-zeroconf

The 1.0.0 release was unintended and was yanked from PyPI (see the
1.0.0 release notes). The root cause was that master's
`[tool.semantic_release]` was missing `allow_zero_version = true`,
so when python-semantic-release was upgraded to 10.x the next
release computed 0.148.0 -> 1.0.0 instead of staying within the
0.x line.

This change brings master's release config in line with the
release-0.x branch (commit 812a2b3, 'feat: trigger semantic
releases for 0.x branch'):

- Add `allow_zero_version = true` so 0.x is treated as the
  active major and breaking-change commits bump 0.x.y, not 1.0.0.
- Add the `release-0.x` branch matcher and exclude it from the
  `noop` (prerelease) match so future releases off either branch
  stay in the 0.x line.
- Reset `version` in pyproject.toml and `__version__` in
  src/zeroconf/__init__.py from 1.0.0 back to 0.148.0 (the last
  intended release) so the next release computes from 0.148.0.