Skip to content

Conversation

jaywink
Copy link
Member

@jaywink jaywink commented Oct 17, 2025

Didn't add a changelog, is it needed for this?

Pull Request Checklist

  • Pull request is based on the develop branch
  • Pull request includes a changelog file. The entry should:
    • Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
    • Use markdown where necessary, mostly for code blocks.
    • End with either a period (.) or an exclamation mark (!).
    • Start with a capital letter.
    • Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.
  • Code style is correct (run the linters)

@jaywink jaywink requested a review from a team as a code owner October 17, 2025 11:10
🚀 Professional support
-----------------------

Enterprise quality support for Synapse including SLAs is available as part of an
Copy link
Contributor

Choose a reason for hiding this comment

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

Didn't add a changelog, is it needed for this?

Yes, everything usually gets a changelog.

19070.doc

Update ESS support and doc links to point to the new domain.

@jaywink jaywink force-pushed the jaywink/fix-ess-customer-portal-link branch from ef4f7e0 to c023020 Compare October 20, 2025 07:20
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