Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Maintenance: create automation to publish v2 docs under next alias #1718

Closed
1 of 2 tasks
dreamorosi opened this issue Sep 27, 2023 · 2 comments · Fixed by #1756
Closed
1 of 2 tasks

Maintenance: create automation to publish v2 docs under next alias #1718

dreamorosi opened this issue Sep 27, 2023 · 2 comments · Fixed by #1756
Assignees
@dreamorosi
Labels
automation This item relates to automation completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Milestone
Version 2.0

Comments

@dreamorosi
Copy link
Contributor

Summary

In #1717 we have created an automation that allows us to publish the content of the v2 branch to npmjs.com. As a continuation of that task we should extend that workflow to publish the documentation for that branch under the next alias whenever a pre-release is made.

Why is this needed?

So that customers can have documentation about the new features as soon as it's available.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.
@dreamorosi dreamorosi added documentation Improvements or additions to documentation automation This item relates to automation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) confirmed The scope is clear, ready for implementation labels Sep 27, 2023
@dreamorosi dreamorosi added this to the Version 2.0 milestone Sep 27, 2023
@dreamorosi dreamorosi self-assigned this Sep 27, 2023
@dreamorosi dreamorosi mentioned this issue Sep 27, 2023
Closed
2 tasks
@dreamorosi dreamorosi mentioned this issue Oct 19, 2023
Merged
9 tasks
@dreamorosi dreamorosi linked a pull request Oct 19, 2023 that will close this issue
chore(ci): add workflow to publish v2 docs on merge #1756
Merged
9 tasks
@github-actions
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Oct 19, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 1, 2023

This is now released under v1.14.1 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
automation This item relates to automation completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Powertools for AWS Lambda (TypeScript)
Status: Shipped
Milestone
Version 2.0
Development

Successfully merging a pull request may close this issue.

chore(ci): add workflow to publish v2 docs on merge aws-powertools/powertools-lambda-typescript
1 participant
@dreamorosi