docs: update microsite configs

Signed-off-by: Camila Belo <camilaibs@gmail.com>

docs/releases/v1.19.0.md

@@ -10,11 +10,63 @@ A huge thanks to the whole team of maintainers and contributors as well as the a
 
 ## Highlights
 
-TODO: @backstage/discoverability-maintainers will add an entry for the insightful homepage.
+### Node.js v18 + v20
+
+The supported versions of Node.js are now v18 and v20. Be sure to update the `engine` field in your root `package.json` accordingly and update your Dockerfile base images, for example to `node:18-bookworm-slim`.
+
+### New default `start` command for backends
+
+Backend packages now use the new `package start` implementation by default. This new version uses module loaders rather than a Webpack build for transpilation. The largest difference from the old version is that the backend process is now restarted on change, rather than using Webpack hot module reloads. When using SQLite the database state is serialized and stored in the parent process across restart, which requires a [migration to the new backend system](https://backstage.io/docs/backend-system/building-backends/migrating). If you have yet to migrate to the new system it is recommended that you set the `LEGACY_BACKEND_START` environment variable when starting the backend to keep the old behavior.
+
+### **BREAKING**: Allow passing undefined `labelSelector` to `KubernetesFetcher`
+
+`KubernetesFetch` no longer auto-adds `labelSelector` when an empty string is passed.
+This is only applicable if you have a custom ObjectProvider implementation, as build-in `KubernetesFanOutHandler` already does this.
+
+Contributed by [@szubster](https://github.com/szubster) in [#20541](https://github.com/backstage/backstage/pull/20541)
+
+### **DEPRECATION**: Catalog GraphQL Backend Package
+
+This package has been deprecated, consider using [@frontside/backstage-plugin-graphql-backend](https://www.npmjs.com/package/@frontside/backstage-plugin-graphql-backend) instead.
+
+### **DEPRECATION**: `.icon.svg` Extension Support
+
+Support for the `.icon.svg` extension has been deprecated and will be removed in a future release. Please migrate existing usage to either inline the SVG elements in a `<SvgIcon>` component from MUI, or switch to a regular `.svg` asset import.
+
+### Insightful Homepage
+
+You can now create an Insightful homepage to show your users their recent and top visited activity in Backstage. Add [this](https://github.com/backstage/backstage/tree/master/plugins/home#page-visit-homepage-component-homepagetopvisited--homepagerecentlyvisited) plugin to track your users’ recent navigation history in your Backstage database and display it in the Backstage Homepage using the customizable Recent and Top visits components (`<HomePageTopVisited />` and `<HomePageRecentlyVisited />`)and the extensible Visits API interface. This feature is released with an example that extends the Visits API with LocalStorage as an alternative storage solution for user visit activity.
+
+### New plugin: Kubernetes Clusters
+
+This plugin lets you view Kubernetes clusters as an admin.
+
+### New feature: New Pinniped Auth Provider Module
+
+This module provides a Pinniped auth provider implementation for the auth backend.
+
+Contributed by [@RubenV-dev](https://github.com/RubenV-dev) in [#19846](https://github.com/backstage/backstage/pull/19846)
+
+## More Movement Toward the New Backend System
+
+Since the last release, a lot of contributions have been made toward migrating features to support [the new backend system](https://backstage.io/docs/backend-system/).
+
+The following backend plugins were migrated:
+
+- jenkins
+- nomad
+- sonarqube
+- playlist
+
+The Kubernetes backend broadened its backend system feature set, with a new extension point. For the catalog backend, some new modules were added, including GitHub org and Microsoft/Azure.
+
+If you would like to help out with these efforts, check out [this issue](https://github.com/backstage/backstage/issues/18301)!
 
 ## Security Fixes
 
-This release does not contain any security fixes.
+Some improvements were made in the configuration schemas, ensuring that no secret fields could be read outside of a backend context.
+
+The `lerna` package in newly scaffolded Backstage repositories is now of version >7 which has security fixes.
 
 ## Upgrade path
 

microsite/docusaurus.config.js

@@ -178,7 +178,7 @@ module.exports = {
             position: 'left',
           },
           {
-            to: 'docs/releases/v1.18.0',
+            to: 'docs/releases/v1.19.0',
             label: 'Releases',
             position: 'left',
           },

microsite/sidebars.json

@@ -1,6 +1,7 @@
 {
   "releases": {
     "Release Notes": [
+      "releases/v1.19.0",
       "releases/v1.18.0",
       "releases/v1.17.0",
       "releases/v1.16.0",