Skip to content

Maintenance: remove v1 workflows from v2 before merge #1616

Closed
@rubenfonseca

Description

@rubenfonseca
Contributor

Summary

We should remove the v1 workflows from the code before merging the v2 code.

Why is this needed?

When we started creating specific workflows for v2, we created separate files. We should now remove the v1 workflows, so they won't interfere with the release process of v2.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

  • This request meets Lambda Powertools Tenets
    Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

Activity

added
triagePending triage from maintainers
internalMaintenance changes
and removed
triagePending triage from maintainers
on Oct 19, 2022
self-assigned this
on Oct 19, 2022
linked a pull request that will close this issuechore(ci): remove v1 workflows #1617on Oct 19, 2022
github-actions

github-actions commented on Oct 20, 2022

@github-actions
Contributor

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments 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.

removed
pending-releaseFix or implementation already in dev waiting to be released
on Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    Participants

    @rubenfonseca@heitorlessa

    Issue actions

      Maintenance: remove v1 workflows from v2 before merge · Issue #1616 · aws-powertools/powertools-lambda-python