Skip to content

Conversation

@Ilia-TheNetworkFirm
Copy link
Contributor

AWS Bedrock Qwen models announcement: https://aws.amazon.com/blogs/aws/qwen-models-are-now-available-in-amazon-bedrock/
AWS Bedrock Deepseek model announcement: https://aws.amazon.com/blogs/aws/deepseek-v3-1-now-available-in-amazon-bedrock/

AWS Bedrock Deepseek

  • deepseek.v3-v1:0

AWS Bedrock Qwen

  • qwen.qwen3-32b-v1:0
  • qwen.qwen3-235b-a22b-2507-v1:0
  • qwen.qwen3-coder-30b-a3b-v1:0
  • qwen.qwen3-coder-480b-a35b-v1:0

Readme

  • Added open_weights example to README.md

README.md Outdated
- `knowledge` _(optional)_: String — Knowledge-cutoff date in `YYYY-MM` or `YYYY-MM-DD` format
- `release_date`: String — First public release date in `YYYY-MM` or `YYYY-MM-DD`
- `last_updated`: String — Most recent update date in `YYYY-MM` or `YYYY-MM-DD`
- `open_weights` _(optional)_: Boolean - Indicate the model’s trained weights are publicly available
Copy link
Contributor

Choose a reason for hiding this comment

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

This is actually required p sure

@rekram1-node
Copy link
Contributor

/oc update the open_weights description in the readme, it is actually a required field not an optional one

@opencode-agent
Copy link
Contributor

opencode-agent bot commented Oct 29, 2025

Perfect! I've successfully updated the README to remove the "(optional)" marking from the open_weights field in the schema reference section. The field is now correctly documented as required rather than optional.

The change I made:

  • Before: - open_weights _(optional)_: Boolean - Indicate the model's trained weights are publicly available
  • After: - open_weights: Boolean - Indicate the model's trained weights are publicly available

This now aligns with the TOML example on line 98 and addresses the pull request review comment that noted this field is actually required.

New%20session%20-%202025-10-29T14%3A50%3A59.441Z
opencode session  |  github run

@rekram1-node rekram1-node merged commit 4319913 into sst:dev Oct 29, 2025
1 check passed
@rekram1-node
Copy link
Contributor

Thanks!

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