Package Details: changie 1.24.0-2

Git Clone URL: https://aur.archlinux.org/changie.git (read-only, click to copy)
Package Base: changie
Description: Automated changelog tool for preparing releases with lots of customization options.
Upstream URL: https://github.com/miniscruff/changie
Keywords: changelog
Licenses: MIT
Submitter: bephinix
Maintainer: bephinix
Last Packager: bephinix
Votes: 1
Popularity: 0.000000
First Submitted: 2021-09-17 14:47 (UTC)
Last Updated: 2026-03-01 21:28 (UTC)

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

bephinix commented on 2026-03-01 21:30 (UTC)

@Blacksmoke16 Fixed. All changie env variables are unset for the check/test section.

Blacksmoke16 commented on 2026-02-24 05:29 (UTC)

I ran into an interesting scenario resulting from https://github.com/miniscruff/changie/pull/828. I have a CHANGIE_CUSTOM_AUTHOR env var defined, and when trying to install changie the check() step is failing seemingly because of it. I.e. because the test suite doesn't have a corresponding custom value configured:

==> Starting check()...
?       github.com/miniscruff/changie   [no test files]
Error: custom value provided but not configured: Author
--- FAIL: TestFullRun (0.20s)
    e2e_test.go:90: creating tempdir: /tmp/TestFullRun4292748213/001
    e2e_test.go:51: expected 'custom value provided but not configured: Author' to be nil
Error: invalid argument "blah-blah-blah" for "changie next"
Error: invalid argument "v1.2.3" for "changie next"

Maybe there's a way to exclude CHANGIE_ env vars from impacting the test suite?

bephinix commented on 2022-07-29 16:55 (UTC) (edited on 2022-07-29 16:55 (UTC) by bephinix)

Thank you for your suggenstions, @lmartinez-mirror.

I have update the PKGBUILD to match the go package guidelines and list git as a make dependency.

In addition to this, go tests provided by upstream are now also executed during the test stage.

lmartinez-mirror commented on 2022-07-20 15:35 (UTC)

Hi, a couple things here:

  • This package needs git in its makedepends, otherwise it won't properly handle the source.
  • Could you explain why the prepare() function needs to rename the source directory?

I would suggest looking at the Go packaging guidelines for a general idea of how this should be written.