Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.22 Release Blog Post #2337

Merged
merged 59 commits into from
Apr 1, 2025
Merged

0.22 Release Blog Post #2337

merged 59 commits into from
Apr 1, 2025

Conversation

Ben8t
Copy link
Member

@Ben8t Ben8t commented Mar 12, 2025

No description provided.

@github-project-automation github-project-automation bot moved this to To review in Pull Requests Mar 12, 2025
Copy link

cloudflare-workers-and-pages bot commented Mar 12, 2025

Deploying kestra-io with  Cloudflare Pages  Cloudflare Pages

Latest commit: 9d6eb70
Status: ✅  Deploy successful!
Preview URL: https://8414e556.kestra-io.pages.dev
Branch Preview URL: https://blog-release-0-22.kestra-io.pages.dev

View logs

@Ben8t Ben8t marked this pull request as ready for review March 28, 2025 11:26

### Sharing Namespace Files

Namespace files can now be shared and reused simply by referencing a given `namespace` directly in your script task. If you define multiple namespaces, Kestra will fetch the corresponding namespace files in the same order the namespaces are listed. If you have the same file(s) defined in multiple namespaces, the later namespaces will override files from earlier ones.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you define multiple namespaces, Kestra will fetch the corresponding namespace files in the same order the namespaces are listed. If you have the same file(s) defined in multiple namespaces, the later namespaces will override files from earlier ones.

The two statements here look contradictory to me. The first one implies that the value will be taken from the starting namespaces in the list, while the second statement implies the value will be taken from the end of the list.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What it means is that it checks your list in a descending order with priority given to later listed namespaces. Sort of first in, first out.

- Improvements to flow filters in the UI (Filter flows by text, filter by multiple labels)
- As part of our continuous improvements to the No-Code Editor, we're releasing a Beta version of a Multi-Panel Editor. To enable this Beta feature, navigate to `Settings` and toggle the `Multi Panel Editor` on.

Our website performance has also significantly improved following Nuxt 2 to 3 migration, including a redesigned plugin page for easier navigation of plugin properties and outputs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the plugin docs redesign is clear enough

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be cool to add a gif to the blog to show the improved navigation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that idea

@anna-geller anna-geller merged commit 62b62ca into main Apr 1, 2025
1 check passed
@anna-geller anna-geller deleted the blog/release-0-22 branch April 1, 2025 12:01
@github-project-automation github-project-automation bot moved this from To review to Done in Pull Requests Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants