Robin Candau pushed to branch main at Arch Linux / Packaging / Packages / ansible-language-server
Commits: 8713d460 by Robin Candau at 2024-07-22T11:50:03+02:00 Add necessary steps to update the package - - - - - 1 changed file: - README.md Changes: ===================================== README.md ===================================== @@ -1,6 +1,6 @@ # ansible-language-server -## Versioning and updating the package +## Versioning history and general explanations about the PKGBUILD The Ansible language server used to have its [own repository](https://github.com/ansible/ansible-language-server) but, at some point, upstream dediced to archive it and merge it into their [vscode plugin repository](https://github.com/ansible/vscode-ansible/issues/1134). @@ -10,3 +10,10 @@ A [request has been made](https://github.com/ansible/vscode-ansible/discussions/ In the mean time, we got the [nvchecker integration](https://gitlab.archlinux.org/archlinux/packaging/packages/ansible-language-server/-/blob/main/.nvchecker.toml?ref_type=heads) looking for ansible-language-server new releases via the [npm registry](https://www.npmjs.com/package/@ansible/ansible-language-server) (which has specific releases/versioning for it). The lack of tagging on the source repo side forces us to use a `_commit` mechanism in the PKGBUILD to point to the commit that bumped the version of ansible-language-server in the associated [package.json file](https://github.com/ansible/vscode-ansible/blob/main/packages/ansible-language-server/package.json), matching the version from the npm registry (you can use `View git blame` on the "version" line of the package.json file in GitHub to see which upstream commit bumped it). Unfortunately, the lack of tagging in the upstream repo for the Ansible language server itself also prevents us to add the usual `pkgver()` verification mechanism (e.g. verify that `$_commit` indeed points to the commit used for the tag that matches `$pkgver`) but, in the current state of things, this is probably the best we can come up with. + +## Updating the package + +- Look for new releases in the [npm registry](https://www.npmjs.com/package/@ansible/ansible-language-server?activeTab=versions) (`.nvchecker.toml` is set up to follow this source) +- Update `$pkgver` (and `$pkgrel` if needed) accordingly +- Retrieve the upstream commit that updated the version matching the one from the npm registry in the associated [package.json](https://github.com/ansible/vscode-ansible/blob/main/packages/ansible-language-server/package.json) file (from GitHub, select the line containing the version and click `View git blame` to retrieve it) and update `$_commit` accordingly +- Update checksums (e.g. by running `updpkgsums`, from the `pacman-contrib` package) View it on GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/ansible-language-server/-/commit/8713d460318daa334cf6ccfdfe774dca7595bbf1 -- View it on GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/ansible-language-server/-/commit/8713d460318daa334cf6ccfdfe774dca7595bbf1 You're receiving this email because of your account on gitlab.archlinux.org.
