Re: Pat v0.17.0 released

19 views
Skip to first unread message

Jan Peterson

unread,
Jun 1, 2025, 10:36:29 PMJun 1
to pat-users

I installed pat this evening with go install github.com/la5nta/pat@latest as described on the getpat.io site, but it installed 0.16.0 (Pat v0.16.0 (823b991) darwin/amd64 - go1.22.2).  Has the “latest” tag not been updated yet?

 

73 de KD7ZWV
  -jan-

 

From: pat-...@googlegroups.com <pat-...@googlegroups.com> on behalf of LA5NTA <martin.h...@gmail.com>
Date: Sunday, May 25, 2025 at 10:46
To: pat-users <pat-...@googlegroups.com>
Subject: Pat v0.17.0 released

Pat v0.17.0 has been released, and binaries for Linux, macOS and Windows are available at https://github.com/la5nta/pat/releases.

Changes:
* Add Configuration page to web GUI
* Add optional message download prompting with size limits
* Add Reply All message action
* Major improvements to attachment handling:
  - Include attachments when forwarding messages
  - Add button to remove attachments
  - Fix attachments not retained when adding more to the same message
  - Improve attachment layout
* Templates:
  - Add support for multi-line prompt in text templates
  - Add CLI command 'templates' for managing forms/templates
  - Add support for template sequence numbers
  - Fix UTF-8 BOM handling in templates
  - Fix empty attached_text form values panic
* Fix Safari GPS timestamp issues
* Fix AGWPE timeout issues
* Fix FBB protocol turnover handling when all messages are deferred and/or rejected

For more details, see milestones/v0.17.0 and compare/v0.16.0...v0.17.0.

--
73 de LA5NTA / Martin

--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/pat-users/f0d120d7-274c-42c2-9fa0-b0b5c5ad2420n%40googlegroups.com.

Martin Hebnes Pedersen

unread,
Jun 2, 2025, 1:58:39 AMJun 2
to Jan Peterson, pat-users
Hi,

It's probably a cache that is stale. Please try @v0.17.0 instead of @latest to force it to update :)

-- 
73 de LA5NTA / Martin
Reply all
Reply to author
Forward
0 new messages