Skip to content

Maintenance: phase out docs publishing to GitHub Pages #1509

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
Closed
1 of 2 tasks
dreamorosi opened this issue Jun 19, 2023 · 3 comments · Fixed by #1513
Closed
1 of 2 tasks

Maintenance: phase out docs publishing to GitHub Pages #1509

dreamorosi opened this issue Jun 19, 2023 · 3 comments · Fixed by #1513
Assignees
@sthulb
Labels
automation This item relates to automation completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@dreamorosi
Copy link
Contributor

Summary

To complete the migration to the new GitHub Org and docs infrastructure, we need to remove from the Docs workflow all the steps that push the docs to GitHub pages, as well as disabling the feature in the repo settings.

Why is this needed?

So that the docs are published only to the new destination.

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 triage This item has not been triaged by a maintainer, please wait internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Jun 19, 2023
@dreamorosi dreamorosi added automation This item relates to automation confirmed The scope is clear, ready for implementation and removed triage This item has not been triaged by a maintainer, please wait labels Jun 19, 2023
@dreamorosi dreamorosi mentioned this issue Jun 19, 2023
Merged
9 tasks
@dreamorosi
Copy link
Contributor Author

The versions.json file in the repo doesn't match with the one in S3 (1.9.0 and its latest alias are missing).

This results in the docs not being available for the latest version.

This was referenced Jun 19, 2023
Merged
Closed
@dreamorosi dreamorosi linked a pull request Jun 20, 2023 that will close this issue
chore(ci): remove GH pages #1513
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 Jun 23, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jun 23, 2023 •
edited by dreamorosi
Loading

This is now released under version 1.10.0!

@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 Jun 23, 2023
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sthulb sthulb

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

Successfully merging a pull request may close this issue.

chore(ci): remove GH pages aws-powertools/powertools-lambda-typescript
2 participants
@sthulb @dreamorosi