Changelog for python3-packit-0.104.0-1.fc39.noarch.rpm :

* Fri Nov 15 2024 Packit - 0.104.0-1- Packit configuration file can now have a placeholder top-level key `_` that is ignored when read. This is useful for storing yaml anchors in complex config files, e.g.:```yaml_: base-test: &base-test job: tests fmf_path: .distrojobs: - <<:
*base-test trigger: pull_request manual_trigger: true - <<:
*internal-test trigger: commit use_internal_tf: true```(#2378)- You can now define `with_opts` and `without_opts` in target-specific configuration of `copr_build` job to build with `--with` and `--without` rpmbuild options. (#2463)- Resolves: rhbz#2325040
* Sun Nov 10 2024 Packit - 0.103.0-1- Packit now supports and defaults to `fast_forward_merge_into` syntax via `--dist-git-branches-mapping` in `dist-git init`. (#2456)
* Tue Oct 22 2024 Packit - 0.102.2-1- Fixed passing list of resolved bugs when running `packit propose-downstream` or `packit pull-from-upstream`. (#2447)- Resolves: rhbz#2321004
* Fri Oct 11 2024 Packit - 0.102.1-1- We have fixed an issue that was introduced during the unification of the interface for passing resolved Bugzillas / Jira tickets to the `sync-release` or `bodhi_update` jobs. (#2442)- `packit validate-config` now checks for the existence of downstream package. (#2436)- Packit now allows building VM images via CLI without any Copr repository specified. (#2434)- Resolves: rhbz#2318003
* Fri Oct 04 2024 Packit - 0.102.0-1- Check for `upstream_project_url` presence in the configuration when `pull_from_upstream` job is configured was removed from `validate-config`, as this is no longer required. (#2423)- `packit init` now adds working directories that are used in `packit prepare-sources` into the `.gitignore` file in the same directory where Packit config resides. (#2431)- Previously, `create-update` command took `--resolve-bugzillas` option and `propose-downstream` command took `--resolve-bug` option. The options have been unified into `--resolve-bug` for better user experience. If you used `create-update` with `--resolve-bugzillas` you have to use `--resolve-bug` (or shorthand `-b`) now instead. (#2428)- Resolves: rhbz#2316445
* Wed Sep 18 2024 Packit - 0.101.1-1- In the user configuration file, it\'s possible to set `default_parse_time_macros`, e.g. might be helpful in situations like [packit/packit-service#2514](https://github.com/packit/packit-service/issues/2514). (#2408)- Packit now allows to configure mock bootstrap feature setup of Copr projects with a new `bootstrap` configuration option. (#2411)- Resolves: rhbz#2313250
* Fri Sep 06 2024 Packit - 0.101.0-1- Packit now supports passing custom arguments to various static analyzers through `--csmock-args` CLI option and `csmock_args` configuration. (#2402)- When synching a new release Packit is now able to fast forward a specified merge to a configured list of branches. Use the `dist_git_branches` new syntax as in this example: `{\"rawhide\": {\"fast_forward_merge_into\": [\"f40\"]}, \"fedora-stable\": {}}` (#2363)- Resolves: rhbz#2310376
* Sat Aug 24 2024 Packit - 0.100.3-1- `dist-git init` command now allows `upstream-git-url` not to be specified. (#2387)- Resolves: rhbz#2306481
* Thu Aug 15 2024 Packit - 0.100.2-1- Update to version 0.100.2- Resolves: rhbz#2300464
* Thu Aug 01 2024 Packit - 0.100.1-1- Dummy release to test the \"build in side tags\" new feature!- Resolves: rhbz#2300464
* Mon Jul 29 2024 Packit - 0.100.0-1- `packit pull-from-upstream` now allows omitting `upstream_project_url` in the configuration in which case the interaction with the upstream repository is skipped during release syncing. (#2354)- We have implemented a CLI support for Koji builds against CBS Koji instance. (#2267)
* Thu Jul 18 2024 Fedora Release Engineering - 0.99.0-2- Rebuilt for https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild
* Fri Jul 12 2024 Packit - 0.99.0-1- Update to version 0.99.0
* Thu Jul 04 2024 Packit - 0.98.0-1- Packit now updates its own, not yet merged, pull requests instead of creating new ones for new releases. (#2204)- Resolves: rhbz#2295821
* Fri Jun 21 2024 Packit - 0.97.3-1- We have fixed a bug that caused inconsistency between the promised environment variables (from the docs) and the environment that has been actually provided. Now you should have access to `PACKIT_UPSTREAM_REPO` and `PACKIT_DOWNSTREAM_REPO`, if they have been cloned already, in the `post-upstream-clone` action. (#2327)- Resolves: rhbz#2293661
* Mon Jun 17 2024 Nikola Forró - 0.97.2-2- Rebuilt for Python 3.13- Resolves: rhbz#2291573
* Thu Jun 06 2024 Packit - 0.97.2-1- We have fixed the syncing of ACLs for `propose-downtream` for CentOS Stream. (#2318)- Resolves: rhbz#2290733
* Fri May 17 2024 Packit - 0.97.1-1- We have fixed the behaviour for `dist-git init` command when `upstream-git-url` argument is specified.- Resolves: rhbz#2278839
* Wed May 15 2024 Packit - 0.97.0-1- Add a `scan-in-osh` subcommand in the CLI to perform a scan through OpenScanHub. By default, it performs a full scan of the packages and a differential scan can be performed through `--base-srpm` option. (#2301)- When running `dist-git init` command from CLI, you can pass a command to specify a git URL of the project. (#2308)
* Mon Apr 22 2024 Packit - 0.95.0-1- `packit dist-git init` now allows specifying `--version-update-mask` option and also any arbitrary top-level configuration options. (#2288)- We have fixed Packit auto-referencing Upstream Release Monitoring bug for release syncing to CentOS Stream. (#2284)- Resolves: rhbz#2276194
* Mon Apr 08 2024 Packit - 0.94.2-1- Packit previously put the \"[packit]\" string as a prefix in the subject of pull-from-upstream commits. Now the prefix is no longer there - this is made unnecessary noise in autochangelog. This affects the default. Custom action can still override this behavior. (#2263)- We have fixed a race condition that could occur when multiple `copr_build` jobs sharing a Copr project but having different targets were running at the same time. (#2274)- Resolves: rhbz#2273977
* Thu Mar 28 2024 Packit - 0.94.1-1- `packit validate-config` now checks whether `upstream_project_url` is set if `pull_from_upstream` job is configured. (#2254)- `Resolves` is changed to `Resolves:` for the dist-git commit since that\'s the correct format for CentOS Stream 9. (#2260)- Resolves: rhbz#2272077
* Sun Mar 17 2024 Packit - 0.94.0-1- Added new configuration options `status_name_template` and `allowed_builders`.- Resolves rhbz#2266037
* Mon Feb 26 2024 Packit - 0.93.0-1- Packit now checks the version to propose against the version in specfile and doesn\'t create downgrade PRs. (#2239)
* Mon Feb 19 2024 Packit - 0.92.0-1- Packit now supports `trigger: ignore` which can be used for templating by using the YAML. (#2234)- Packit now searches for bugzilla about new release created by Upstream Release Monitoring to reference each time it syncs the release downstream. (#2229)- Resolves rhbz#2264878
* Wed Feb 07 2024 Packit - 0.91.0-1- We have introduced new CLI command `packit dist-git init` that initializes Packit configuration for release automation in dist-git repository. (#2225)- `packit validate-config` now checks whether the Upstream Release Monitoring for the package is correctly configured if `pull_from_upstream` job is present in the configuration. (#2226)- There is a new global configuration option `parse_time_macros` that allows to configure macros to be explicitly defined or undefined at spec file parse time. (#2222)- Resolves rhbz#2259201
* Sun Jan 28 2024 Packit - 0.90.0-1- `pull-from-upstream` and `propose-downstream` commands now have the `--sync-acls` option that enables syncing the ACLs between dits-git repo and fork. The default behaviour was, however, changed to not sync the ACLs. (#2214)- Packit now properly handles exceptions when syncing ACLs during release syncing. (#2213)
* Thu Jan 25 2024 Fedora Release Engineering - 0.89.0-2- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Fri Jan 19 2024 Packit - 0.89.0-1- We have fixed a bug in handling chroot-specific configuration once the chroots themselves are updated. (#2194)
* Sun Jan 07 2024 Packit - 0.88.0-1- We have fixed a bug preventing the release from being synced downstream if the changelog to be set is empty. (#2183)- Resolves rhbz#2257183
* Thu Nov 30 2023 Packit - 0.87.1-1- Packit now links the information related to upstream in PRs opened when syncing a release. (#2173)- Resolves rhbz#2252328
* Fri Nov 24 2023 Packit - 0.87.0-1- Packit now correctly sets the specfile content (e.g. changelog entry) even if it syncs the specfile from upstream the first time. (#2170)- Packit now supports pre-release version in `propose_downstream` and `pull_from_upstream`. A spec file update might be required, see the documentation for more details. (#2149)- Resolves rhbz#2251367
* Mon Nov 20 2023 Packit - 0.86.2-1- Packit _0.86.1_ was not released on PyPI due to an internal bug, it should be fixed in this release.
* Mon Oct 30 2023 Packit - 0.85.0-1- Packit no longer downloads sources excluded using spec file conditions. (#2132)
* Mon Oct 16 2023 Packit - 0.84.0-1- We have adjusted how we include the resolved bugzillas in the commit messages created when syncing the release downstream so that the resolved bugzillas are included in changelog when using %autochangelog. (#2126)- Packit now properly cleans up the branch after syncing the release which should prevent unwanted files (e.g.tarballs) being committed in dist-git. (#2125)- Packit no longer accepts `packit.json` or `.packit.json` as a configuration file name. (#2123)- Packit now updates ACL of a dist-git fork when creating dist-git PRs to allow users and groups with commit rights to the original dist-git repo to push directly to a source branch. (#2112)- We have fixed an issue that prevented you from running the jobs on the GitLab.com due to failing resolution of the upstream/downstream relationship for the cloned project. (#2120)- We have fixed an issue that you could encounter when running the Packit from the CLI that caused misinterpretation of the repository to be an upstream repo instead of a downstream. (#2117)- Resolves rhbz#2244381
* Fri Oct 06 2023 Packit - 0.83.0-1- We have fixed an issue that prevented automated allowlisting in the Packit Service. (#2113)- Packit now also detects resolved bugs in the default update notes (created from changelog diff) and assigns these when submitting the Bodhi updates. (#2111)- Packit now exports `PACKIT_UPSTREAM_PACKAGE_NAME`, `PACKIT_DOWNSTREAM_PACKAGE_NAME` and `PACKIT_CONFIG_PACKAGE_NAME` also in the `changelog_entry` action. (#2103)
* Fri Sep 29 2023 Packit - 0.82.0-1- You can now specify bugs resolved by an update by `-b` or `--resolve-bug` option for `propose-downstream` and `pull-from-upstream` commands. The values will be added by default to the changelog and commit message and provided in `commit-message` and `changelog-entry` actions as `PACKIT_RESOLVED_BUGS` env variable. (#2094)- Resolves rhbz#2240355
* Sat Sep 23 2023 Packit - 0.81.0-1- Packit now supports the `pkg_tool` option in the config (at the top-level or with specific packages when using the monorepo syntax). This option can be used for switching between `fedpkg` or `centpkg`. (#2085)- When updating the `Version` tag during `propose_downstream` or `pull_from_upstream`, Packit now tries to update referenced macros (if any) rather than overwriting the references. (#2087)- If you have concerns about Packit uploading new archives to lookaside cache before creating a pull request, you can newly set `upload_sources` to False to disable this. (#2086)- We have fixed a bug that could cause duplicit PRs to be created when using the `commit-message` action. (#2080)- Packit now supports `commit-message` action that can be used to override the default commit message produced by Packit during `propose-downstream` or `pull-from-upstream`. Please pay attention to our [documentation](https://packit.dev/docs/configuration/actions#commit-message) with regards to the usage of this action. (#2070)
* Fri Sep 08 2023 Packit - 0.80.0-1- 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)
* Mon Aug 07 2023 Packit - 0.78.2-1- 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)
* Tue Aug 01 2023 Packit - 0.78.1-1- Temporarily disabled test dependencies on Fedora Rawhide because of missing `python3-deepdiff`. (#2008)
* Thu Jul 20 2023 Fedora Release Engineering - 0.77.0-2- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Sat Jun 17 2023 Packit - 0.77.0-1- 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)
* Fri May 26 2023 Packit - 0.76.0-1- 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. This decision has been made to lower the load on Copr from the temporary Copr projects created, mainly, for the PR builds. If you are releasing your packages to Copr, please use the new setting `follow_fedora_branching`. Already existing projects are not affected by this change and it is also not enforced with the custom Copr repositories. (#1970)
* Fri Apr 28 2023 Packit - 0.75.0-1- 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)
* Sun Apr 16 2023 Packit - 0.74.0-1- 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)
* Thu Apr 06 2023 Packit - 0.73.0-1- Packit now supports monorepo configuration in CLI (#1864)
* Fri Mar 31 2023 Packit - 0.72.0-1- Packit now preserves `autorelease` macro during `propose_downstream` and `pull_from_upstream`. (#1904)
* Sat Mar 25 2023 Packit - 0.71.0-1- `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)
* Mon Mar 20 2023 Packit - 0.70.0-1- Now packit uses the `get_current_version` action defined by the user to retrieve version before updating the specfile %setup macro (if any). (#1886)
* Sun Mar 05 2023 Packit - 0.69.0-1- `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)
* Mon Feb 20 2023 Packit - 0.68.0-1- 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)
* Fri Feb 03 2023 Packit - 0.67.0-1- Packit now sanitizes changelog messages in order not to break spec file parsing. (#1841)
* Fri Jan 20 2023 Packit - 0.66.0-1- 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)
* Thu Jan 19 2023 Fedora Release Engineering - 0.65.2-2- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Wed Jan 04 2023 Packit - 0.65.2-1- No changes. This is a fixup release for sake of Packit deployment.
* Thu Dec 22 2022 Packit - 0.65.1-1- Packit now puts the correct release number into the changelog when the `Release` tag is reset during `propose-downstream`. (#1816)
* Fri Dec 09 2022 Packit - 0.65.0-1- 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)
* Fri Dec 02 2022 Packit - 0.64.0-1- `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.Source0 is no longer treated specially, but as `spec_source_id` is `Source0` by default, Source0 is still being uploaded by default unless `spec_source_id` is overriden. (#1778)