Packit now supports monorepo configuration in CLI (#1864)

Packit now preserves `autorelease` macro during `propose_downstream` and `pull_from_upstream`. (#1904)

`upstream_tag_template` is now also used when looking for the latest version tag in Git. This allows upstream repositories to mix different tag-patterns in the same repository, but consider only one to tell the latest version. (#1891)

Now packit uses the `get_current_version` action defined by the user to retrieve version before updating the specfile %setup macro (if any). (#1886)

`packit validate-config` now correctly checks glob-patterns in `files_to_sync`. (#1865)
Aliases logic was updated to account for the upcoming Fedora release (Bodhi now marks such release as `frozen`). (#1863)
Command `packit validate-config` now provides details about errors when it cannot parse the config file. (#1861)
Packit does fewer API calls when searching for the package configuration file in remote repositories. (#1846)
`--update-release`/`--no-update-release` now affects only `Release`, not `Version`. (#1857)
Packit now provides `PACKIT_PROJECT_VERSION` environment variable when running `changelog-entry` action. (#1853)

Packit now requires bodhi in version 7.0.0 at minimum. (#1844)
You can now use `--srpm` option with the `packit build locally` CLI command. (#1810)

Packit now sanitizes changelog messages in order not to break spec file parsing. (#1841)

When configuring Copr chroot (target in Packit terminology) specific configuration, make sure to specify `additional_modules` as a string containing module names separated with a comma, example: "httpd:2.4,python:4". (#1826)
Target-specific configuration for Copr builds can now be defined and Packit will set it for the appropriate Copr chroots. (#1822)
You can now specify `update_release: false` in the configuration to tell Packit not to change the `Version` and `Release` in the spec file. It works the same as `--no-update-release` (renamed from now deprecated `--no-bump`) in the CLI. (#1827)
Packit now supports setting `module_hotfixes` for Copr projects. (#1829)
All Copr projects created by Packit now default to `enable_net=False`. Our documentation stated this but it wasn't the case. This is now corrected. (#1825)

Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild

No changes. This is a fixup release for sake of Packit deployment.

Packit now puts the correct release number into the changelog when the `Release` tag is reset during `propose-downstream`. (#1816)

Packit now correctly handles a race condition when it tries to create bodhi updates for builds that are not yet tagged properly. CLI exprience was also improved for this case. (#1803)
Packit now resets the `Release` tag during `propose-downstream` if the version is updated and the `Release` tag has not explicitly been overridden in the upstream specfile. (#1801)

`packit propose-downstream` now uploads all remote sources (those specified as URLs) and the source specified by `spec_source_id` (whether remote or not) to lookaside. Previously, only Source0 was uploaded.

Packit now correctly finds SRPM when rpmbuild reports warnings when it parses the spec file. (#1772)
When packit.yaml is present in the repo but is empty, Packit now produces a better error message instead of an internal Python exception. (#1769)

Fixed an issue due to which the repository was never searched for a specfile if 'specfile_path' was not specified, and 'specfile_path' was always set to '<repo_name>.spec'. (#1758)
Packit is now able to generate automatic Bodhi update notes including a changelog diff since the latest stable build of a package. (#1747)

Fixed an issue with version and release being updated even if `--no-bump` flag was specified. Also fixed an issue when `None` appeared in release instead of a number. (#1753)