Skip to content

Docs: Clarify task-sdk publishing vs publish-docs workflow (#64350)#64711

Closed
Mayankaggarwal8055 wants to merge 3 commits intoapache:mainfrom
Mayankaggarwal8055:fix-task-sdk-docs
Closed

Docs: Clarify task-sdk publishing vs publish-docs workflow (#64350)#64711
Mayankaggarwal8055 wants to merge 3 commits intoapache:mainfrom
Mayankaggarwal8055:fix-task-sdk-docs

Conversation

@Mayankaggarwal8055
Copy link
Copy Markdown
Contributor

@Mayankaggarwal8055 Mayankaggarwal8055 commented Apr 4, 2026

This PR resolves the contradiction in task-sdk publishing instructions.

Problem

The documentation described task-sdk as “not yet published”, while it is actually available on the documentation site. However, it is not published via the publish-docs workflow.

Changes

  • Clarified that Task SDK docs are available on the site
  • Specified that they are not published via the publish-docs workflow
  • Removed task-sdk from publishing command examples
  • Ensured consistency across documentation

Impact

Improves clarity for release managers and removes ambiguity in publishing instructions.

closes: #64350

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch labels Apr 4, 2026
@potiuk
Copy link
Copy Markdown
Member

potiuk commented Apr 4, 2026

This is wrong. Task-sdk is already publishable. Removing instructions seems like AI-generated, unverified change. Please avoid that. and Verify all changes.

also closed the issue because it was wrong.

@potiuk potiuk closed this Apr 4, 2026
@potiuk
Copy link
Copy Markdown
Member

potiuk commented Apr 4, 2026

Please next time verify the changes and issues that AI proposes. (and always use Generated-By when you use AI as instructed in the contributing guides.

You can fix the "new format" instead.

@Mayankaggarwal8055
Copy link
Copy Markdown
Contributor Author

Thanks @potiuk for the clarification.

I understand that my assumption about task-sdk publishing was incorrect. I should have verified it more thoroughly before submitting the PR.

I’ll be more careful with validation going forward and will follow the Generated-By guideline when using AI assistance.

I’ll look into the “new format” issue you mentioned and try to contribute there instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Resolve contradiction in task-sdk publishing instructions

2 participants