Skip to content

Maintenance: fix docs publishing during release #1491

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 9, 2023 · 1 comment · Fixed by #1513
Closed
1 of 2 tasks

Maintenance: fix docs publishing during release #1491

dreamorosi opened this issue Jun 9, 2023 · 1 comment · 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

Note
This is not related to #1490, the issue happens when publishing to a different destination.

When making a release, the very last step consists in rebuilding the docs and deploying them on GitHub Pages with the update ARNs of the public Lambda Layers for Powertools.

The workflow is currently failing with an error that suggests that mike is not able to push the latest tag due to it existing already.

We need to investigate and understand why this is happening and fix it.

Why is this needed?

So that we can make an automated release that includes all the steps.

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 9, 2023
@dreamorosi dreamorosi added confirmed The scope is clear, ready for implementation automation This item relates to automation and removed triage This item has not been triaged by a maintainer, please wait labels Jun 9, 2023
@dreamorosi dreamorosi linked a pull request Jun 23, 2023 that will close this issue
chore(ci): remove GH pages #1513
Merged
9 tasks
@github-project-automation github-project-automation bot moved this from Backlog to Coming soon in Powertools for AWS Lambda (TypeScript) Jun 23, 2023
@github-project-automation github-project-automation bot moved this from Backlog to Coming soon in AWS Lambda Powertools for TypeScript Jun 23, 2023
@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.

@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Jul 11, 2023
@dreamorosi dreamorosi added completed This item is complete and has been merged/shipped and removed confirmed The scope is clear, ready for implementation labels Jul 11, 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