-
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)
-
Wed Mar 30 2022 Packit <hello@packit.dev> - 0.48.0-1
- `packit source-git update-dist-git` and `packit source-git update-source-git` now check the synchronization of source-git and dist-git repositories prior to doing the update. If the update can't be done, for example, because the histories have diverged, the command provides instructions on how to synchronize the repositories. A `--force` option is available to try to update the destination repository anyway.
- Downstream synchronization of the Packit configuration file (aka `packit.yaml`) should be fixed. (#1532)
- Packit will no longer error out when trying to create a new Copr repository when it is already present (caused by a race condition). (#1527)
- Interactions with Bodhi should be now more reliable when creating Bodhi updates. (#1528)
-
Thu Mar 17 2022 Packit Service <user-cont-team+packit-service@redhat.com> - 0.47.1-1
- When using Packit CLI for creating Bodhi updates, you can now set `fas_username` and `fas_password`
in your Packit user config to not be asked about that when the command is executed. (#1517)
-
Tue Mar 08 2022 Packit Service <user-cont-team+packit-service@redhat.com> - 0.47.0-1
- When specfile is being generated, and both `specfile_path` and
`downstream_package_name` are not set, Packit now correctly resolves this
situation and sets `specfile_path` to the name of the upstream repo suffixed
with ".spec". (#1499)
- We are now building SRPMs for Packit's own PRs in Copr. For more info see #1490 and
https://packit.dev/docs/configuration/#srpm_build_deps (#1490)
- All source-git-commands were updated to append a `From-source-git-commit` or `From-dist-git-commit`
Git-trailer to the commit messages they create in dist-git or source-git, in order to
save the hash of the commits from which these commits were created. This information
is going to be used to tell whether a source-git repository is in sync with the
corresponding dist-git repository. (#1488)
- Spec file and configuration file are no more automatically added to the list of files
to sync when the `new files_to_sync` option is used. The old `synced_files` option is
deprecated. (#1483)
- We have added a new configuration option for Copr builds `enable_net` that allows you to
disable network access during Copr builds. It is also complemented by
`--enable-net/--disable-net` CLI options if you use Packit locally. (#1504)
-
Wed Feb 16 2022 Packit Service <user-cont-team+packit-service@redhat.com> - 0.46.0-1
- Synchronization of default files can now be disabled using a new config
`files_to_sync`. Key `sync_files` is now deprecated. (#1483)
- Packit now correctly handles colons in git trailer values in source-git commits. (#1478)
- Fedora 36 was added to the static list of `fedora-` aliases. (#1480)
-
Fri Feb 04 2022 Packit Service <user-cont-team+packit-service@redhat.com> - 0.45.0-1
- A new `packit source-git update-source-git` command has been introduced for
taking new changes from dist-git (specified by a revision range) to source-git.
These may include any changes except source code, patches and `Version` tag
changes in the spec file. ([packit#1456](https://github.com/packit/packit/pull/1456))
- There's a new configuration option `create_sync_note` that allows you to
disable creating of README by packit in downstream. ([packit#1465](https://github.com/packit/packit/pull/1465))
- A new option `--no-require-autosetup` for `source-git init` command has been
introduced. Please note that source-git repositories not using `
%setup -q
` may
not be properly initialized. ([packit#1470](https://github.com/packit/packit/pull/1470))
-
Thu Jan 20 2022 Packit Service <user-cont-team+packit-service@redhat.com> - 0.44.0-1
- Packit now correctly finds the release, even if you don't use the version as
the title of the release on GitHub. ([packit#1437](https://github.com/packit/packit/pull/1437))
- Local branches are now named as `pr/{pr_id}` when checking out a PR, even
when it's not being merged with the target branch. This results in the NVR
of the build containing `pr{pr_id}` instead of `pr.changes{pr_id}`. ([packit#1445](https://github.com/packit/packit/pull/1445))
- A bug which caused ignoring the `--no-bump` and `--release-suffix` options
when creating an SRPMs from source-git repositories has been fixed. Packit
also doesn't touch the `Release` field in the specfile unless it needs to be
changed (the macros are not expanded that way when not necessary). ([packit#1452](https://github.com/packit/packit/pull/1452))
- When checking if directories hold a Git-tree, Packit now also allows `.git`
to be a file with a `gitdir` reference, not only a directory. ([packit#1458](https://github.com/packit/packit/pull/1458))