Update CHANGELOG for version 0.5.2 (#328)

Updated changelog for version 0.5.2 release.

chore: promote changelog for release (#320)

Add note that using config file will not handle import-names

Clarify the usage of ni-python-styleguide with flake8.

fix: Work around "No module named 'pkg_resources'" by pinning setupto…

…ols to <82 (#275)

* fix: Work around "No module named 'pkg_resources'"

pin black to version that support Python < 3.10 still (#262)

* pin black to version that still support 3.9

* Apply suggestion from @mshafer-NI

* Update pyproject.toml

Co-authored-by: Brad Keryan <brad.keryan@ni.com>

---------

Co-authored-by: Brad Keryan <brad.keryan@ni.com>

update publishing flow to use ni/python-actions (#227)

* update publishing flow to use ni/python-actions

* github: Split Publish-Package.yml jobs according to security best practices

* github: Restore versioning policy

* github: Fix next version update

---------

Co-authored-by: Brad Keryan <brad.keryan@ni.com>

Dev/fix command being over aggressive (#185)

* make filter actually work

* log when we fail to read a file, what file it was

* make a failing test

* make it pass

* print the exception in the test

* switch to pathspec for globbing/matching in fix

* move pathspec to core tooling section

* format / linter issues

* simplify

Ignore F401 for __init__.py files (#173)

* Ignore F401 for __init__.py files

These files routinely import other modules without immediately using
them with the intention of making them available to the importing
module. Moreover, they are rarely even supposed to be used within the
same __init__.py file. Marking all of them 'noqa: F410' is redundant.

* Update docs/Coding-Conventions.md

---------

Co-authored-by: mshafer-NI <matthew.shafer@ni.com>

Update pyproject.toml

the release tooling is failing to bump this, so bump it by hand.

Also ignore D102 Missing docstring in public method in tests (#148)

* Also ignore D102 Missing docstring in public method in tests

* bump patch num