If anyone else noticed, it seems GNU ELPA tried to build Eglot even
before the next version bump and it failed because I hadn't published
external-completion.el yet as a :core package.  So I did that now. I
presume it should eventually fix itself.  If you think I'm wrong, please
let me know.  Thanks.

João

On Sat, Dec 10, 2022 at 10:03 PM ELPA update <do.not.reply@elpa.gnu.org>
wrote:

> The build scripts failed to build the tarball
> for version 1.9.0.20221210.112248 of the package eglot.
> You can consult the latest error output in the file
> "eglot-build-failure.txt" in the GNU-devel ELPA archive web site.
>
> You can also try and reproduce the error locally as follows:
>
>     git clone --single-branch git://git.sv.gnu.org/emacs/elpa.git
>     cd elpa
>     make                 # Setup the infrastructure
>     make packages/eglot  # Create a worktree of the package
>     make build/eglot     # Build the tarballs into archive(-devel)/
>
> ## The current error output was the following:
>
> ======== Building tarball archive-devel/eglot-1.9.0.20221210.112248.tar...
> Current revision is already desired revision!
> Checking dependencies: ((emacs (26 3)) (jsonrpc (1 0 14)) (flymake (1 2
> 1)) (project (0 3 0)) (xref (1 0 1)) (eldoc (1 11 0)) (seq (2 23))
> (external-completion (0 1)))
> Deleting temp files: nil
> Build error for archive-devel/eglot-1.9.0.20221210.112248.tar: (error
> "Unknown required package: external-completion")
> ######## Build of package archive-devel/eglot-1.9.0.20221210.112248.tar
> FAILED!!
>


-- 
João Távora