Packit CLI now provides a new command `pull-from-upstream`, offering the same functionality as `propose-downstream` but suited for usage from the dist-git repository with Packit configuration placed there. This was primarily added to help reproduce the behaviour of the service's [pull_from_upstream job](https://packit.dev/docs/configuration/downstream/pull_from_upstream). (#2063)
Packit now exposes `PACKIT_PACKAGE_NAME`, `PACKIT_UPSTREAM_PACKAGE_NAME` and `PACKIT_DOWNSTREAM_PACKAGE_NAME` environment variables to all actions. (#2061)
We have fixed a bug in `packit source-git init` caused by changed behaviour in a newer version of rpmbuild. (#2048)

Packit's license in RPM specfile is now confirmed to be SPDX compatible. (#2026)
`source-git init --ignore-missing-autosetup` help was improved to be less confusing. (#2016) (#2017)

Temporarily disabled test dependencies on Fedora Rawhide because of missing `python3-deepdiff`. (#2008)

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

Packit now includes dist-git branch in the title of the PRs for `propose-downstream` and `pull-from-upstream`. (#1996)
We have fixed an issue with `files_to_sync` filters not being applied properly. (#1977)

Unsuccessful Image Builder requests now provide error details so you can fix the Image configuration. (#1981)
Copr projects created by Packit will not follow the Fedora branching from now on.

Detection of `%autorelease` usage in dist-git spec file during `propose-downstream` and `pull-from-upstream` has been improved and Packit will always preserve it. (#1949)
Changed build tool to hatchling and moved metadata to `pyproject.toml`. (PEP621) (#1913)
Respect `upstream_ref` for tags that start with "a", "b", "c", "e", "n", "r", "s". This was caused by an issue with a `branches` prefix being treated as a set of letters to remove. (#1943)
Reset `Release` field in dist-git spec file to `1` when the version in upstream spec file is not up-to-date with the release that triggered `propose_downstream`. (#1940)
Correctly catch the logs, if any of the user actions fail during the propose-downstream. (#1939)
`packit source-git` related commands can skip dist-git repos, where the git trailer is not found, when looking for the right dist-git dir where to work. (#1938)
More monorepo related fixes. (#1946, #1947, #1948)

Allow configuring tmt tests with fmf root outside of git root. (#1936)
Removed adding the "Signed-off-by" tag to commits created by Packit. (#1934)
Packit's source_git functionality installs/loads the `_packitpatch` script in a more reliable manner that doesn't rely on deprecated setuptools functionality. (#1926)

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)