fix: Disallow log level 'trace'

[zoispag]

Closes #759

[piksel]

LGTM

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (main@8b95e8c). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #765   +/-   ##
=======================================
  Coverage        ?   43.06%           
=======================================
  Files           ?       24           
  Lines           ?     1356           
  Branches        ?        0           
=======================================
  Hits            ?      584           
  Misses          ?      713           
  Partials        ?       59           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b95e8c...ba56d26. Read the comment docs.

[zoispag]

@simskij is there some permission issue with the runner, that my commit failed and yours not?

[simskij]

@zoispag No, I just fixed the workflow. My commit was mainly meant to trigger a rerun and check if it worked 😅

[harrytheeskimo]

Please update the Wiki at https://containrrr.dev/watchtower/notifications/ to note that trace is disallowed.
It's still shown as an option.

--notifications-level (env. WATCHTOWER_NOTIFICATIONS_LEVEL): Controls the log level which is used for the notifications. If omitted, the default log level is info. Possible values are: panic, fatal, error, warn, info, debug or trace.

[piksel]

@harrytheeskimo just a FYI; you can directly suggest an edit by clicking the pen icon in the top right of the documentation!

[harrytheeskimo]

@piksel thanks, I did try that at the time yesterday, but the page is restricted:

You need to fork this repository to propose changes.

Sorry, you’re not able to edit this repository directly—you need to fork it and propose your changes from there instead.

[simskij]

Yeah, the flow is that you make an edit in your fork and then create a PR against this repo. We might need to be clearer about that. Sorry if it tripped you up.