Re: [NonGNU ELPA] Htmlize version 1.57

Re: [NonGNU ELPA] Htmlize version 1.57

[Hrvoje Nikšić]

Hi,

Is there a way to have ELPA track the "stable" branch rather than
"master"? The email is just wrong, as htmlize 1.57 has *not* been
released - I've just pushed the version bump to the branch that holds
development ("master").

Hrvoje

On Thu, Aug 26, 2021 at 11:08 AM ELPA update <do.not.reply@elpa.gnu.org> wrote:
>
> Version 1.57 of package Htmlize has just been released in NonGNU ELPA.
> You can now find it in M-x package-list RET.
>
> Htmlize describes itself as:
>   Convert buffer text and decorations to HTML.
>
> More at https://elpa.nongnu.org/nongnu/htmlize.html
>
> Recent NEWS:
>
> htmlize NEWS -- history of user-visible changes.
>
> * Changes in htmlize 1.51
>
> ** `htmlize-face-overrides' can be used to override Emacs's face
> definitions.
>
>
> * Changes in htmlize 1.47
>
> ** GNU Emacs 21 is no longer supported.
>
>
> * Changes in htmlize 1.45
>
> ** Correctly handle :inherit specifying a list of faces.  (This bug
> would cause an error in AUX TeX buffers.)
>
>
> * Changes in htmlize 1.44
>
> ** Faces specified in the `face' property are now prioritized the same
> way that Emacs redisplay does it: faces that appear earlier have
> precedence over those that appear later.
>
>
> * Changes in htmlize 1.41
>
> ** `before-string' and `after-string' overlay properties are now
> recognized by htmlize and inserted into the HTML.
>
> ** Images specified by `display' property are recognized and inserted
> into the HTML as <img src=...>.
>
> *** If the image data comes from a file, the image will be rendered as
> a relative URI that would resolve to that file.  Images whose data
> comes from a string will be rendered inline as data: URIs.  The flag
> `htmlize-force-inline-images' can be used to force inserting *all*
> images inline as data: URIs.
>
> ** The image's ALT text will be the text that the `display' property is
> replacing, if non-empty.
>
> ** Arbitrary links can now be added to the generated HTML.  If htmlize
> encounters buffer text with `htmlize-link' property, it will wrap the
> text in <a href="uri">...</a>.  If the property value is a string, it
> is interpreted as the URI.  If it is a list, it should be a property
> list whose currently only defined key is :uri.

Re: [NonGNU ELPA] Htmlize version 1.57

[Stefan Monnier via Users list for the GNU Emacs text editor]

Hi Hrvoje,

Hrvoje Nikšić [2021-08-26 11:44:00] wrote:
> Is there a way to have ELPA track the "stable" branch rather than
> "master"? The email is just wrong, as htmlize 1.57 has *not* been
> released - I've just pushed the version bump to the branch that holds
> development ("master").

Right, the general rule is that a release is
made from the commit that changes the `Version:` header, so indeed
setting it to `1.57` before the actual release leads to trouble.

There are various options to avoid the problem:

- One way is to set your `Version:` to something like `1.57-snapshot` or
  `1.57-git` during development (or leave it set at the previous
  release's version) and then set it to `1.57` for the release itself.

- Another is to use a separate branch for the releases.

Since you seem to have a dedicated release branch already, I installed
the patch below to nongnu.git so releases will be made from the
`stable` branch.  Sorry for not noticing earlier,

BTW, the email is sadly right: an htmlize-1.57 package has been released
on http://elpa.nongnu.org/nongnu/htmlize.html :-(


        Stefan


diff --git a/elpa-packages b/elpa-packages
index b7d4a4bd1..4aafd5460 100644
--- a/elpa-packages
+++ b/elpa-packages
@@ -80,7 +80,8 @@
   :readme "README.md")
 
  ("htmlize"		:url "https://github.com/hniksic/emacs-htmlize"
-  :ignored-files ("htmlize.el.html"))
+  :ignored-files ("htmlize.el.html")
+  :release-branch "stable"))
 
  ("inf-clojure"		:url "https://github.com/clojure-emacs/inf-clojure"
   :ignored-files ("test")