Releases: packit/packit
Releases · packit/packit
0.26.0
- Fix construction of the Koji tag for epel branches when running
packit create-update
. (#1122) create-update
now also shows a message about Bodhi requiring the password. (#1127)packit init
correctly picks up sources from CentOS and fetches specfile from CentOS dist-git. (#1106)- Fix translating of the target aliases by treating the highest pending version in Bodhi as
rawhide
. (#1114) - The format of Packit logs is unified for all log levels. (#1119)
- There is a new configuration option
sources
which enables to define sources to override their URLs in specfile.
You can read more about this in our documentation. (#1131)
0.25.0
propose-update
command now respects requested dist-git branches. (#1094)- Improve the way how patches are added to spec file. (#1100)
--koji-target
option of thebuild
command now accepts aliases. (#1052)propose-downstream
on source-git repositories now always uses--local-content
. (#1093)- Don't behave as if
ref
would be always a branch. (#1089) - Detect a name of the default branch of a repository instead of assuming it to be called
master
. (#1074)
0.24.0
0.24.0
- No user-facing changes done in this release.
0.23.0
0.23.0
- The
propose-update
has been renamed topropose-downstream
;propose-update
is now deprecated
to unify the naming between CLI and service. (@jpopelka, #1065) - Our README has been cleaned and simplified. (@ChainYo, #1058)
- The 🍾 comment with the installation instructions has been disabled by default. (@mfocko, #1057)
- More information can be found in our documentation.
- Packit is being prepared to be released in EPEL 8 so it can be consumed in RHEL and CentOS Stream. (@nforro, #1055)
0.22.0
0.22.0
packit init
introduces the--upstream-url
option. When specified,
init
also sets up a source-git repository next to creating a configuration file.- Don't rewrite macros when setting release and version in spec file.
- Fix generation of Copr settings URL for groups.
- Improve processing of the version when proposing a Fedora update.
0.21.0
0.21.0
- The correct source is used when
source_name
is specified. (The problem with the firstSource
tag in a spec file not indexed has been fixed.) - Sanitize potentially problematic characters in a branch name
before creating a copr project name from it. - Default job now includes copr build as well.
0.20.0
0.20.0
- The
fedora-all
,fedora-stable
,fedora-development
andepel-all
chroot aliases are now translated to concrete chroots by consulting Bodhi,
making the transition to new Fedora releases smoother. - A new,
copy_upstream_release_description
option is available in
packit.yaml
. When set totrue
, the GitHub release description is going
to be used to update the changelog in the spec-file, when creating a new
update in Fedora dist-git. When set tofalse
(the default), the subject
lines of the commits included in the release are used to update the changelog. - Fix an issue (#1012) by improving how the current version is discovered.
0.19.0
0.19.0
- Allow syncing full content of the spec-file.
- Let packit create empty patch files from empty commits.
- Check for the existing pull requests in distgit when using
propose-update
. - Allow symlinking absolute path to the archive within repository.
0.18.0
0.18.0
- Packit got new
archive_root_dir_template
config option to get custom archive root dir. You can find more info in the documentation.
0.17.0
0.17.0
Minor changes and fixes
- When adding patches to a specfile, the numbering of source-git patches begins after original patches.
- It is now possible to use globbing pattern when specifying ref in packit config.
upstream_tag_template
is now used for extracting version from git tag.- Specifiying project using CLI is fixed.
- Packit doesn't drop leading zeros in version strings.
- Our contribution guidelines are cleaned up.
--remote
option is now global and available to all the commands.sync-from-downstream --remote
was renamed to--remote-to-push
.--remote
can now be specified in user's config (via
upstream_git_remote
parameter).- packit is now able to generate a patch file with format-patch without leading a/ and b/ in the patch diff.