Fix YAML parsing break in automated-release-blog-post workflow template

[Copilot]

The automated release blog workflow was failing before job execution due to YAML being broken by unindented markdown frontmatter (---) inside the embedded Node script. This PR keeps workflow behavior intact while making the inline template YAML-safe.

• Root cause

  • In .github/workflows/automated-release-blog-post.yml, the blogPost template literal inside run: | had multiline content starting at column 1.
  • Frontmatter delimiters were interpreted as YAML document separators, invalidating the workflow file.

• Change applied

  • Re-indented the embedded markdown template so all lines remain inside the YAML block scalar.
  • Preserved generated markdown format by stripping script indentation at runtime:
    • .replace(/^ {10}/gm, '').trimStart()

• Scope

  • Single-file, workflow-only change.
  • No change to release selection logic, contributor/changelog generation, file naming, or commit behavior.

const blogPost = `
          ---
          slug: release-${safeTag}
          title: "🚀 SHAFT ${tag}: What's New and Why You Should Upgrade Today"
          ...
          `
  .replace(/^ {10}/gm, '')
  .trimStart();

[netlify]

✅ Deploy Preview for shaftengine ready!

Name	Link
🔨 Latest commit	bfe0a7d
🔍 Latest deploy log	https://app.netlify.com/projects/shaftengine/deploys/69cc3435a4fa320008bab5b0
😎 Deploy Preview	https://deploy-preview-437--shaftengine.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 88 Accessibility: 93 Best Practices: 100 SEO: 100 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.