|
1 | 1 | --- |
2 | | -title:"GitOpsRelease Notes: March" |
3 | | -description:"Release Notes for Codefresh GitOps" |
| 2 | +title:"Release Notes: March 2025" |
| 3 | +description:"Release Notes for CodefreshPipelines andGitOps" |
4 | 4 | --- |
5 | 5 | ##Features & enhancements |
6 | 6 |
|
@@ -60,6 +60,8 @@ Configuration steps are clearly defined, making the set up process easy to compl |
60 | 60 | ***Configure as an Argo CD Application** to take full advantage of GitOps. |
61 | 61 | ***Add a Git source** to the Runtime so you’re ready to create applications. |
62 | 62 |
|
| 63 | +{% if page.collection == "posts" %} |
| 64 | + |
63 | 65 | ###Pipelines: Easily add secret variables |
64 | 66 |
|
65 | 67 | We've introduced a simpler and more secure way to add secret variables in your pipelines, making it faster and safer to manage sensitive data. Before this update, adding a secret required creating a standard variable, temporarily exposing the value, and manually encrypting it, increasing the risk of accidental exposure. |
@@ -95,12 +97,18 @@ Previously, it was easy to unintentionally override a project-level variable at |
95 | 97 |
|
96 | 98 | For details, see[Order of precedence for user-defined variables]({{site.baseurl}}/docs/pipelines/variables/#order-of-precedence-for-user-defined-variables). |
97 | 99 |
|
| 100 | +{% endif %} |
| 101 | + |
98 | 102 | ##Bug fixes |
99 | 103 |
|
| 104 | +{% if page.collection == "posts" %} |
| 105 | + |
100 | 106 | #####Pipelines |
101 | 107 |
|
102 | 108 | * Helm step does not use latest Helm version 3.14. |
103 | 109 |
|
| 110 | +{% endif %} |
| 111 | + |
104 | 112 | #####GitOps |
105 | 113 |
|
106 | 114 | * Typo in parameter name in the`values.yaml` file of the`gitops-runtime chart`. |