Replies: 1 comment 1 reply
-
Well, you bring different topics, that I've been thinking for a while. Identifying deprecated/archived dependencies is a tricky one, and it may require a big effort to review all Updatecli integration like NPM, GitHub release, etc. but we could definitely start one by one. I also thought about implementing libyear within Updatecli, probably by adding the information to changelogs. Regarding notification, I've been considering adding new action for sending messages on variable platform. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi 👋🏻
Crazy idea here!
We were wondering in a discussion that even though is not updatecli's scope as of today, It would be really nice to be notified in case some project used as a source is deprecated/archived/abandoned somehow. It may happen that we stop receiving pull request notifications from an specific projects and that would be kind of difficult to detect in case you manage many applications as we do.
There could be some indicators (github example):
In case some of this indicators match, updatecli could open an Issue in the GitOps repository specified in the
scm
pointing out that thesource
seems or could be abandoned/deprecated.What do you think ?
Cheers !
Beta Was this translation helpful? Give feedback.
All reactions