-
Notifications
You must be signed in to change notification settings - Fork 4.1k
docs: blog layout update #8472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: blog layout update #8472
Changes from all commits
02774a1
f80adf6
f6e8de8
dfc187b
4bd894d
35767d6
37da898
9bf6bbb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,9 +3,10 @@ title: "goose v1.25.0: Sandboxed, Streamlined, and More Secure" | |
| description: "goose v1.25.0 brings macOS sandboxing, a unified summon extension, rich MCP app UIs, agentic CLI upgrades, and SLSA build provenance." | ||
| authors: | ||
| - debbie | ||
| image: /img/blog/goose-v1-25-0.png | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
This post now declares Useful? React with 👍 / 👎. |
||
| --- | ||
|
|
||
|  | ||
|  | ||
|
|
||
| goose v1.25.0 is here, and it's one of our most significant releases yet. This version brings macOS sandboxing for enhanced security, a major architectural simplification with the unified summon extension, rich UI rendering for MCP apps, and a wave of improvements to agentic CLI providers. Whether you're running goose Desktop or the CLI, there's something in this release for you. | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| /** | ||
| * Copyright (c) Facebook, Inc. and its affiliates. | ||
| * | ||
| * This source code is licensed under the MIT license found in the | ||
| * LICENSE file in the root directory of this source tree. | ||
| */ | ||
| import React from 'react'; | ||
| import Head from '@docusaurus/Head'; | ||
| import {useBlogListPageStructuredData} from '@docusaurus/plugin-content-blog/client'; | ||
| export default function BlogListPageStructuredData(props) { | ||
| const structuredData = useBlogListPageStructuredData(props); | ||
| return ( | ||
| <Head> | ||
| <script type="application/ld+json"> | ||
| {JSON.stringify(structuredData)} | ||
| </script> | ||
| </Head> | ||
| ); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This post switched to the new
/img/blog/tool-descriptions-banner.pngasset, but the hardcoded<head>tags later in the same file still point to.../assets/images/blogbanner-...png. After the rename, that old asset path no longer exists in the build output, soog:image/twitter:imageresolve to 404 and social previews break for this post (and similarly renamed posts in this commit).Useful? React with 👍 / 👎.