-
Thu Aug 25 2022 Packit <hello@packit.dev> - 0.59.0-1
- Packit CLI can now submit VM images in Red Hat Image Builder.
All build-related commands have now consistent `--wait`/`--no-wait` options. (#1666)
- No more annoying issues will be created after a successfull propose downstream. (#1693)
-
Fri Aug 05 2022 Packit <hello@packit.dev> - 0.57.0-1
- BREAKING CHANGE: fixed an issue where the repo was searched for the specfile before checking if 'downstream_package_name' is set, and '<downstream_package_name>.spec' can be used as the 'specfile_path'. (#1663)
-
Thu Jul 14 2022 Packit <hello@packit.dev> - 0.55.0-1
- Packit can now correctly create bodhi updates using the new Bodhi 6 client. (#1651)
-
Wed Jun 29 2022 Packit <hello@packit.dev> - 0.54.0-1
- Packit Bash completion file is no longer needlessly executable. (#1634)
- Transition to Bodhi's new authentication mechanism is now fully complete. (#1635)
-
Wed Jun 22 2022 Packit <hello@packit.dev> - 0.53.0-1
- Packit now works with Bodhi 5 and Bodhi 6 authentication mechanism. (#1629)
- Git ref name that Packit works with during `propose-downstream` is now made more obvious in logs. (#1626)
- Packit now correctly handles creation of custom archives in root while a specfile is in a subdirectory. (#1622)
- Creation of a Bodhi update will not timeout anymore as Packit is now using a more efficient way of obtaining the latest build in a release. (#1612)
-
Wed Jun 08 2022 Packit <hello@packit.dev> - 0.52.1-1
- Fixed a regression where string values for the `targets` and `dist_git_branches` configuration keys were not accepted. (#1608)
-
Thu May 26 2022 Packit <hello@packit.dev> - 0.52.0-1
- Packit will not raise exceptions anymore when creating an SRPM with dangling symlinks. (#1592)
- `packit validate-config` now checks the paths in the package config (path of the specfile,
paths of the files to be synced) relative to the project path (#1596)
- The name of the temporary branch in `_packitpatch` was normalized which fixed applying the patches during `packit source-git init` (#1593)
-
Fri May 13 2022 Packit <hello@packit.dev> - 0.51.0-1
- We have decided to deprecate `metadata` section for job configurations. All
metadata-specific configuration values can be placed on the same level as the job
definition. For now we are in a backward-compatible period, please move your settings
from the `metadata` section. (#1569)
- Packit now correctly removes patches during `packit source-git init` when the
preamble does not contain blank lines. (#1582)
- `packit source-git` commands learnt to replace Git-trailers in commit
messages if they already exist. (#1577)
- Packit now supports `--release-suffix` parameter in all of the related CLI
commands. Also we have added a support for the `release_suffix` option from
configuration to the CLI. With regards to that we have introduced a new CLI
switch `--default-release-suffix` that allows you to override the configuration
option to Packit-generated default option that ensures correct NVR ordering
of the RPMs. (#1586)
-
Thu May 05 2022 Packit <hello@packit.dev> - 0.50.0-1
- When initializing source-git repos, the author of downstream commits created from patch files which are not in a git-am format is set to the original author of the patch-file in dist-git, instead of using the locally configured Git author. (#1575)
- Packit now supports `release_suffix` configuration option that allows you to override the long release string provided by Packit that is used to ensure correct ordering and uniqueness of RPMs built in Copr. (#1568)
- From the security perspective, we have to decided to disable the `create_pr` option for our service, from now on Packit will unconditionally create PRs when running `propose-downstream`.
We have also updated the `propose-downstream` CLI such that it is possible to use `create_pr` from configuration or override it via `--pr`/`--no-pr` options. (#1563)
- The `source-git update-*` commands now check whether the target repository is pristine and in case not raise an error. (#1562)
-
Wed Apr 13 2022 Packit <hello@packit.dev> - 0.49.0-1
- A new configuration option `downstream_branch_name` has been added, which is meant to be used in source-git projects and allow users to customize the name of the branch in dist-git which corresponds to the current source-git branch. (#1555)
- Introduced two new build and test target aliases: `fedora-latest-stable` resolves to the latest stable Fedora Linux release,
while `fedora-branched` resolves to all branched releases (all Fedora Linux release, except `rawhide`). (#1546)
- When using `post_upstream_clone` to generate your spec-file, Packit now correctly checkouts the release before the action is run. (#1542)