Skip to content

Update news for v2026.1#1763

Merged
matthew-white merged 1 commit intomasterfrom
ktuite/update-news
Apr 4, 2026
Merged

Update news for v2026.1#1763
matthew-white merged 1 commit intomasterfrom
ktuite/update-news

Conversation

@ktuite
Copy link
Copy Markdown
Member

@ktuite ktuite commented Apr 3, 2026

Updates news for latest release.

What has been done to verify that this works as intended?

Why is this the best possible solution? Were any other approaches considered?

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Does this change require updates to documentation? If so, please file an issue here and include the link below.

Before submitting this PR, please make sure you have:

  • branched off and targeted the next branch OR only changed documentation/infrastructure (master is stable and used in production)
  • verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

@ktuite ktuite force-pushed the ktuite/update-news branch from b5e735d to 53cfadd Compare April 3, 2026 23:34
@ktuite ktuite force-pushed the ktuite/update-news branch from 53cfadd to aada486 Compare April 3, 2026 23:43
@matthew-white matthew-white merged commit 0895149 into master Apr 4, 2026
10 checks passed
@matthew-white matthew-white deleted the ktuite/update-news branch April 4, 2026 00:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants