-
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
### What would you like to see changed?
In CLI, when prompted to upgrade, I now see:
> To enable automated upgrades, se…
-
What I mean is that, let's use a weapon as an example:
- Unupgraded weapon has 100% energy and space efficiency
- A `-50% energy cost` weapon has 200% EE and 100% SE
- A `-50% cooldown` weapon…
-
This isn't an issue, but I thought it may be of use to you; we forked your Elasticsearch states a while back and just released an automated rolling restart/upgrade to go with it: https://github.com/v…
-
### Problem Statement
[Raising feature request for consideration/refinement following a brief discussion with @seut ]
Storage compatibility is currently only maintained for the previous major re…
-
As the cookiecutter is continually being updated, it might make sense to start cutting releases so that projects using the cookiecutter have a clear cookiecutter version they are based on, and to thin…
-
It would be awesome if we could have the system update itself from the latest Github master commit.
We would need to work out rock solid migration code, as well as figuring out some form of revision …
-
As a user who watches repos with recurring automated PRs that I always ignore, I would like to define a filter that tells PR Focus to automatically ignore fetched PRs that meet the criteria.
For e…
-
Hey, we could consider baking into AMI automated upgrades of Helm-Chart when we make a release, to handle issue with upgrades. Implementing this wouldn't be hard. ArgoCD or [FluxCD](https://fluxcd.io/…
-
### Name and Version
bitnami/external-dns
### What architecture are you using?
None
### What steps will reproduce the bug?
Attempt to upgrade or install the external-dns chart at versio…
-
### Description
When users have a certain line of Node-RED versions which are fine, for example 2.2.X, it would allow FlowForge to automatically trigger upgrades of Node-RED in case of security issue…