Merge release/26.8 into trunk

[wpmobilebot]

Merging release/26.8 into trunk.

Via intermediate branch merge/release-26.8-into-trunk, to help fix conflicts if any:

                            release/26.8  ----o-- - - -
                                               \
           merge/release-26.8-into-trunk        `---.
                                                     \
                                   trunk  ------------x- - -

[dangermattic]

	1 Message
📖	This PR has the Releases label: some checks will be skipped.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Configuration	Release-Alpha
	Build Number	31814
	Version	PR #25461
	Bundle ID	org.wordpress.alpha
	Commit	9b35a68
	Installation URL	6maiq8id2hiu0

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Configuration	Release-Alpha
	Build Number	31814
	Version	PR #25461
	Bundle ID	com.jetpack.alpha
	Commit	9b35a68
	Installation URL	4fr4hn5q3oqq8

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[crazytonyli]

@kean There is a conflict in the Reader.css file, which is modified in both #25456 and the trunk branch. I discarded the changes in #25456 and kept the trunk version. Please feel free to update this PR if the conflict resolution was incorrect.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[crazytonyli]

@kean Actually, I'll merge this PR to keep the release process going. Feel free to create a follow-up PR to address the conflict resolution if needed. Thanks!

[kean]

Thanks for the heads up. I'll review the code in trunk once it merges to ensure everything is still in place.

[crazytonyli]

BTW, here is the diff

<<<<<<< HEAD
/* workaround for CMM-1964 */
.reader-full-post .reader-full-post__story-content {
  a {
    color: var(--main-link-color);
  }
}

.reader-full-post__story-content .wp-block-button {
  a {
    color: var(--color-text);
    font-weight: 500;
    font-size: 1rem;
    text-decoration: none;
  }

  border-radius: 8px;
}

||||||| parent of 26c29afd0a (Fix colors in post inline comment section (#25456))
=======
/* workaround for CMM-1964 */
@media (prefers-color-scheme: dark) {
  .reader-full-post.reader-full-post__story-content a {
      color: var(--main-link-color);
  }
}

.reader-full-post__story-content .wp-block-button {
  a {
    color: var(--color-text);
    font-weight: 500;
    font-size: 1rem;
    text-decoration: none;
  }

  border-radius: 8px;
}

>>>>>>> 26c29afd0a (Fix colors in post inline comment section (#25456))