Closed Phundrak closed 2 years ago
Cool, I tagged the latest master
version as 3.0, which MELPA Stable should soon pick up and build.
This was a slightly rushed release. I was going to create a release too, but a bit more carefully. I'll probably release 3.1 soon.
Okay, I am ready for a release too now. :grinning:
@melpa/maintainers, I'll wait a few days before I create another release, just in case someone wants to add something before then.
IMO releases should be done using a dedicated release commit with summary Release version VERSION
and that commit must update Package-Requires
to VERSION. Then that commit should be tagged, using message Package-Build VERSION
(for consistency with previous release tags). It would also be good to sign both the commit and the tag. After the release a new commit should be created, which changes Package-Requires
to VERSION-git
.
My sisyphus
package can help with that.
Yep, this was definitely half-assed. Happy with any more organised process. The more work it is to make a release, the less I am likely to be the person who does it, but that might not be a bad outcome! 😁
:grimacing:
The issue
The current release on Melpa Stable dates from January 19th, 2020 with commit https://github.com/melpa/package-build/commit/bc06686806d676658b5e962497770e47025c17f1. At that time,
package-build
still used the macrodefmethod
from the packagecl
.Not only has
cl
been deprecated in favor ofcl-lib
, it has now been removed from Emacs. Unfortunately, Cask relies on Melpa Stable to download its required dependencies to run, including the now outdatedpackage-build
version. The lack of(require 'cl)
in the file crashes version 29 of Emacs.A fix for that would be to push a newer version to Melpa Stable with the addition of a new tag/release.
Steps to reproduce:
.cask
directory in$HOME
or$HOME/.config/emacs
)cask init
in a dummy projectpackage-build
.Cask’s logs regarding `package-build`
By modifying Cask’s Melpa source to
melpa.org
instead ofstable.melpa.org
, I no longer have this issue.