Updates for deprecations in goreleaser.

Update goreleaser configuration and example update script to deal with deprecation notices.
Modify readme to conform to the new format standards.
Include deprecation notices in the readme.

Author: tech10

.github/workflows/goreleaser.yml

@@ -33,7 +33,7 @@ jobs:
           # either 'goreleaser' (default) or 'goreleaser-pro'
           distribution: goreleaser
           version: latest
-          args: release --rm-dist
+          args: release --clean
         env:
           GITHUB_TOKEN: ${{ secrets.GIT_PAT }}
           GPG_FINGERPRINT: ${{ steps.import_gpg.outputs.fingerprint }}

.goreleaser.yml

@@ -48,20 +48,7 @@ builds:
         goarch: 386
 archives:
   -
-    replacements:
-      darwin: macOS
-      linux: Linux
-      windows: Windows
-      freebsd: FreeBSD
-      netbsd: NetBSD
-      openbsd: OpenBSD
-      plan9: Plan9
-      dragonfly: DragonFly
-      solaris: Solaris
-      aix: AIX
-      386: i386
-      amd64: x86_64
-      arm64: aarch64
+    rlcp: true
     format_overrides:
       - goos: windows
         format: zip
@@ -88,6 +75,7 @@ changelog:
       - '^docs:'
       - '^release:'
 source:
+  rlcp: true
   enabled: true
   name_template: "{{ .ProjectName }}_source"
   format: "tar.gz"

README.MD

@@ -23,20 +23,25 @@ My goals for this project are to create a stable server for the NVDARemote addon
 
 On the [releases](https://github.com/tech10/nvdaRemoteServer/releases) page, there are compiled binaries for various operating systems and architectures that Go supports. I have made an effort to ensure each binary is a completely static build, and thus, not dependent on any libraries that may or may not be used in different operating systems upon which the program can be run. Since there are numerous systems and configurations available for use, the download and installation of the server's binary builds won't be completely covered in this documentation.
 
+Due to some recent deprecation notices in Goreleaser, the following changes have been made to the archive file format, which will take effect on the next release.
+
+- The architecture format has changed. Most notibly, x86_64 is now amd64, i386 is 386, aarch64 is arm64.
+- Operating system formats have been changed. For the most part, the capital letters have been removed from the operating system formats. Windows is windows, OpenBSD is openbsd, etc. The most significant of these changes is that macOS will be replaced with darwin. Any scripts that update the server from the GitHub releases will need to be updated accordingly, so as to reflect these changes.
+
 Some basic instructions to download and use the binary on Linux using a x86_64 architecture would be the following, for example.
 
 ```console
 # Assume wget is installed.
 # First, download the latest archive.
-$ wget https://github.com/tech10/nvdaRemoteServer/releases/latest/download/nvdaRemoteServer_Linux_x86_64.tar.gz
+$ wget https://github.com/tech10/nvdaRemoteServer/releases/latest/download/nvdaRemoteServer_linux_amd64.tar.gz
 # Use tar to extract the archive and change to the directory.
-$ tar -axf ./nvdaRemoteServer_Linux_x86_64.tar.gz
-$ cd ./nvdaRemoteServer_Linux_x86_64
+$ tar -axf ./nvdaRemoteServer_linux_amd64.tar.gz
+$ cd ./nvdaRemoteServer_linux_amd64
 # Copy the binary to the users bin directory, for example.
 $ cp -a ./nvdaRemoteServer ~/bin/
 # Clean up after yourself by removing what you don't need.
 $ cd ../
-$ rm -r ./nvdaRemoteServer_Linux_x86_64*
+$ rm -r ./nvdaRemoteServer_linux_amd64*
 ```
 
 A sample systemd service file is also available within the archive, which is for use on systems using systemd. Configuration of systemd with this server is outside the scope of this documentation, as there are numerous configurations available for use with systemd.

update-nvdaRemoteServer.sh

@@ -4,8 +4,8 @@
 # and are using systemd for your daemon manager. This will automatically download the latest release.
 # Modify the appropriate variables for your system, and commands, if needed.
 binary="nvdaRemoteServer"
-os="Linux"
-arch="x86_64"
+os="linux"
+arch="amd64"
 program="${binary}_${os}_${arch}"
 check() {
 eval $@