Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Prepare release 7.4.1#11377

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.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
nicoddemus merged 3 commits into7.4.xfromrelease-7.4.1
Sep 2, 2023
Merged

Prepare release 7.4.1#11377

nicoddemus merged 3 commits into7.4.xfromrelease-7.4.1
Sep 2, 2023

Conversation

@github-actions
Copy link
Contributor

Created automatically from manual trigger.

Once all builds pass and it has beenapproved by one or more maintainers, the build
can be released by pushing a tag7.4.1 to this repository.

@nicoddemus
Copy link
Member

As commented in#11126 (comment), I'm also including some improvements to our CI workflow:

  • Build the package only once, and test on all platforms.
  • Deploy is now triggered manually via an Action, which is then responsible for tagging the repository after the package has been uploaded successfully.

This new workflow has been used successfully already inpytest-mock andpytest-xdist.

Once this is merged, I will port the workflow back tomain (seems easier to test and make sure it is working here during a release, rather than implementing this onmain and then backporting).

@nicoddemusnicoddemusforce-pushed therelease-7.4.1 branch 3 times, most recently frombc11330 todde5825CompareSeptember 2, 2023 11:34
* Build the package only once, and test on all platforms.* Deploy is now triggered manually via an Action, which is then responsible for tagging the repository after the package has been uploaded successfully.* Drop 'docs': we nowadays rely on readthedocs preview PR builds.
@nicoddemusnicoddemus mentioned this pull requestSep 2, 2023
@nicoddemus
Copy link
Member

Waiting on#11378 in order to be able to triggerdeploy (because ofworkflow_dispatch, which needs to land onmain first).

@nicoddemus
Copy link
Member

Now that#11378 was merged, I triggered the deploy workflow; it is now sitting there waiting approval.@bluetech would you like to do the honors?

@bluetech
Copy link
Member

Seems like it was published, only the tag push failed.

@nicoddemus
Copy link
Member

Seems like it was published, only the tag push failed.

Yes, bummer. I pushed the tag manually, and will commit a fix to that problem.

We need the checked out repository in order to push the tag.
@nicoddemusnicoddemus merged commit82eb86f into7.4.xSep 2, 2023
@nicoddemusnicoddemus deleted the release-7.4.1 branchSeptember 2, 2023 15:41
nicoddemus added a commit to nicoddemus/pytest that referenced this pull requestSep 2, 2023
nicoddemus added a commit to nicoddemus/pytest that referenced this pull requestSep 2, 2023
nicoddemus added a commit to nicoddemus/pytest that referenced this pull requestSep 2, 2023
nicoddemus added a commit that referenced this pull requestSep 2, 2023
Merge pull request#11377 from pytest-dev/release-7.4.1
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@bluetechbluetechbluetech approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@nicoddemus@bluetech@pytestbot
[8]ページ先頭
©2009-2025 Movatter.jp