Skip to content

Commit

Permalink
Release version 0.9.0 (#269)
Browse files Browse the repository at this point in the history
  • Loading branch information
jstasiak committed Sep 18, 2023
1 parent ea9be1c commit c84a457
Show file tree
Hide file tree
Showing 5 changed files with 32 additions and 5 deletions.
27 changes: 27 additions & 0 deletions CHANGELOG
Original file line number Diff line number Diff line change
@@ -1,3 +1,30 @@
--------------
Release: 0.9.0
--------------

Date: 2023-09-18

Added:

* Add hash capabilities to OUI (#225, amitmi704)

Fixed:

* **Backwards incompatible:** Handle RFC 6164 IPv6 addresses (don't reserve first IP
address in point-to-point subnets) ($267, Damien Claisse)
* **Technically backwards incompatible:** Fix for is_loopback behaviour – consider
``IPNetwork('::1/128')`` to be loopback (#222, #223, niels)
* Include tutorials in source distributions (#215, Louis Sautier)
* Fix a documentation typo (#242, Wouter)
* Fix print syntax in the documentation to be Python 3 compatible (#221, François Magimel)
* Fix the Sphinx syntax in the documentation (#220, François Magimel)

Other:

* Update the databases (#266, Jakub Stasiak)
* Deprecate Python 3.6 (#263, Jakub Stasiak)
* Eliminate unnecessary evals (#228, KOLANICH)

--------------
Release: 0.8.0
--------------
Expand Down
2 changes: 1 addition & 1 deletion docs/source/changes.rst
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
===========================
What's new in netaddr 0.8.0
What's new in netaddr 0.9.0
===========================

.. include:: ../../CHANGELOG
4 changes: 2 additions & 2 deletions docs/source/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -48,9 +48,9 @@
# built documents.
#
# The short X.Y version.
version = '0.8.0'
version = '0.9.0'
# The full version, including alpha/beta/rc tags.
release = '0.8.0'
release = '0.9.0'

# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
Expand Down
2 changes: 1 addition & 1 deletion docs/source/index.rst
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
===========================
netaddr 0.8.0 documentation
netaddr 0.9.0 documentation
===========================

.. toctree::
Expand Down
2 changes: 1 addition & 1 deletion netaddr/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"""A Python library for manipulating IP and EUI network addresses."""

#: Version info (major, minor, maintenance, status)
__version__ = '0.8.0'
__version__ = '0.9.0'
VERSION = tuple(int(part) for part in __version__.split('.'))
STATUS = ''

Expand Down

6 comments on commit c84a457

@kloczek
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like it is missing 0.9.0 git tag.

@jstasiak
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kloczek good spot, thank you – I just pushed it.

@kloczek
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you 👍 😄

If may I drop copy of some ticket template content which I'm time to time creating against repos which I have packages in distributions on which I'm working.

RFE: is it possible to start making github releases?🤔

On create github release entry is created email notification to those whom have set in your repo the web UI Watch->Releases.
gh release can contain additional comments (li changelog) or additional assets like release tar balls (by default it contains only assets from git tag) however all those part are not obligatory.
In simplest variant gh release can be empty because subiekt of the sent email contains git tag name.

I'm asking because my automation process uses those email notifications by trying to make preliminary automated upgrades of building packages, which allows saving some time on maintaining packaging procedures.
Probably other people may be interested to be instantly informed about release new version as well.

Documentation and examples of generate gh releases:
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://cli.github.com/manual/gh_release_upload/
https://github.com/marketplace/actions/github-release
https://pgjones.dev/blog/trusted-plublishing-2023/
jbms/sphinx-immaterial#281 (comment)
tox target to publish on pypi and make gh release https://github.com/jaraco/skeleton/blob/928e9a86d61d3a660948bcba7689f90216cc8243/tox.ini#L42-L58

@jstasiak
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it sounds sensible. Does this look ok? https://github.com/netaddr/netaddr/releases/tag/0.9.0

@kloczek
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep .. 👍
My automation was able to process email notification and do automatic upgrade by reuse existing build procedure with bumped version 😄

@jstasiak
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice.

Please sign in to comment.