Bot releases are hidden (Show)
Published by Hexagon 6 months ago
foreground
to run
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.18...1.0.0-rc.19
Published by Hexagon 6 months ago
fix(packaging): Fix another regression bug related to moving to jsr.io
Published by Hexagon 6 months ago
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.16...1.0.0-rc.17
Published by Hexagon 6 months ago
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.15...1.0.0-rc.16
Published by Hexagon 6 months ago
Important! Minimum Deno Version: Pup now require Deno version 1.42.0
or later. If you're using an older version, you'll need to upgrade Deno before upgrading Pup.
deno.land/x
to JSR.io**/_._
is default for watcher config. **/*.*
is correct.deno.land/x/udd
with @check/deps
@cross/deps
for cross-runtime filesystem operationsdeno.land/x/hexagon/service
with @cross/service
for cross-runtime service installationdeno.land/x/std/
with @std/
from jsrdeno.land/x/dax
with dax-sh
for a cross runtime shelldeno.land/x/zod
with npm:zod
@cross/utils
instead of Deno built-ins for cross runtime ansi console output, argument parsing, process management and more.@cross/env
to handle enviroment variables across runtimes.@cross/test
insted of Deno test runner, to utilize the native test runners of Node, Deno and Bun.Published by Hexagon 7 months ago
1.0.0-rc.13
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.13...1.0.0-rc.14
Published by Hexagon 7 months ago
1.38.0
or later. If you're using an older version, you'll need to upgrade Deno before upgrading Pup.--unstable-kv
to maintain compatibility as --unstable
is being phased out in Deno 2.0.Deno.serve
instead of the deprecated Deno.serveHttp
for alignment with current Deno practices.--unstable
in CI andlt
with lessThan
, gt
with greaterThan
, and deferred
with native Promises.Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.12...1.0.0-rc.13
Published by Hexagon 11 months ago
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.11...1.0.0-rc.12
Published by Hexagon 12 months ago
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.10...1.0.0-rc.11
Published by Hexagon about 1 year ago
Commit History: 1.0.0-rc.9...1.0.0-rc.10
Full Changelog: pup.56k.guru/changelog.html
Published by Hexagon about 1 year ago
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.8...1.0.0-rc.9
Published by Hexagon about 1 year ago
SIGTERM
instead of SIGKILL
to terminate processes. By @Leokuma in https://github.com/Hexagon/pup/pull/40
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.7...1.0.0-rc.8
Published by Hexagon about 1 year ago
plugins.options
, update json schema.start
, stop
and terminate
were returning “Action failed” even though they worked by @Leokuma in https://github.com/Hexagon/pup/pull/39
Full Changelog: https://hexagon.github.io/pup/changelog.html
Commit history: https://github.com/Hexagon/pup/compare/1.0.0-rc.6...1.0.0-rc.7
Published by Hexagon about 1 year ago
0.195.0
to 0.196.0
6.0.6
to 6.0.7
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.5...1.0.0-rc.6
Published by Hexagon about 1 year ago
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.4...1.0.0-rc.5
Published by Hexagon over 1 year ago
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.3...1.0.0-rc.4
Published by Hexagon over 1 year ago
terminateTimeout
(default 30) and terminateGracePeriod
(default 0) to both process and global scopes by @Leokuma in https://github.com/Hexagon/pup/pull/37
service
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.2...1.0.0-rc.3
Published by Hexagon over 1 year ago
Full Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.1...1.0.0-rc.2
Published by Hexagon over 1 year ago
--
correctlyFull Changelog: https://github.com/Hexagon/pup/compare/1.0.0-rc.0...1.0.0-rc.1
Published by Hexagon over 1 year ago
Pup has now achieved enough stability to enter the Release Candidate phase. Here is a brief summary of the significant changes and enhancements implemented during the Beta phase:
Major refactoring of the core modules was conducted to improve efficiency and stability.
Several bug fixes were made in different parts of the software, especially in the process module, the worker runner, and the web interface plugin.
The upgrader module underwent a significant revamp, introducing upgrade channels, support for initial installs and better error handling. We've also implemented more granular permission checks to align with the principle of least privilege. Pup now requests only the specific permissions necessary for each operation, enhancing overall security. Note that these security improvements only cover Pup, permissions of child processes must be taken care of explicitly as usual.
New features added to web interface plugin, such as telemetry status, process status, and details of the selected process in the side bar.
The logger module was improved by moving internal logs from temporary to persistent storage. Allowing for the new command pup logs
which allow filtering using --start/end <iso-time>
, --severity <error|warn|...>
etc.
A new maintenance loop was added to purge internal logs and status after a set number of hours.
Breaking changes were introduced with the move to Deno KV for storing internal states and logs. This transition required a fresh install of Pup and the use of the --unstable flag in Deno. If you're upgrading from an early version, run pup upgrade --channel prerelease
twice to make sure you're all good.
The load balancer module was enhanced with features for backend health tracking, error handling, and redirection.
Significant enhancements were made to the CLI to improve functionality and user experience.
Moving forward, our focus will shift to bug hunting and overall stability improvements. We greatly appreciate any feedback from users during this final testing phase. Please be aware that while this release candidate is close to the final version, it might still contain some bugs.
It's important to note that Pup can currently only operate with the --unstable flag. However, this is automatically managed by the installer/upgrader. As soon as Deno stabilizes KV, the --unstable flag will be automatically removed during the upgrade process.