Thoughts about release note URLs #106
Replies: 7 comments 2 replies
-
Thank you for testing and good points. The I agree, image names might have been more "standard" even though they also vary - many different sources of the same service. So they'd need one entry for each source. Could still work though, so good point. And another reason is that the list of containers with updates are just container names currently, not referencing image so it was easier to just iterate through that. Lastly - they're not printed in the main output because I considered it being tied to the notifications. But you're right, maybe there should be an option for it! Currently doing a overhaul of it all. Edit: And about the |
Beta Was this translation helpful? Give feedback.
-
Please look at the notify-rewrite branch discussion for further points, changes and questions. |
Beta Was this translation helpful? Give feedback.
-
Maybe the output could be unified? |
Beta Was this translation helpful? Give feedback.
-
Yes it could, but I know some people have used the output for custom things - so I rather not clutter that. Good points and will consider for future changes! Thank you. |
Beta Was this translation helpful? Give feedback.
-
I've just now realized that this is a reqiurement in order to make it work 😅 So yeah, that condition would be good. Either that, or you reference the source file on github and fetch it every time the script is invoked. But those aspects don't touch the issue with on what to use as the lookup key. |
Beta Was this translation helpful? Give feedback.
-
Sorry I've not replied - I wanted to push the notification rewrite first and then see if I can work on this - just havnt found the time. |
Beta Was this translation helpful? Give feedback.
-
Added a line to urls.list to fix a "url missing". It's related to vaultwarden so put it right after vaultwarden-server. Since this topic is under discussion not sure what the approved procedure is. A PR seems like overkill to add one url. diff --git a/notify_templates/urls.list b/notify_templates/urls.list |
Beta Was this translation helpful? Give feedback.
-
I've just tested the latest release regarding the release notes feature. For me it didn't work as expected. My email body looked like this:
That wasn't very satisfying :-) Wouldn't it be better to match the release note URL by the image URL? Container names can vary, but the image source URL is unique.
Another thing I've noticed is that the release notes URLs aren't printed when running the check via the console. Is there a reason not to do that?
Despite that I think this could become a great and very useful feature! Thank you.
Beta Was this translation helpful? Give feedback.
All reactions