Skip to content

Update pyproject to version 1.5.0#962

Merged
TanYiQing merged 3 commits intoreleases/1.5from
users/yqtan/update-pyproject-15
Apr 23, 2026
Merged

Update pyproject to version 1.5.0#962
TanYiQing merged 3 commits intoreleases/1.5from
users/yqtan/update-pyproject-15

Conversation

@TanYiQing
Copy link
Copy Markdown
Collaborator

@TanYiQing TanYiQing commented Apr 22, 2026

- [ ] I've updated CHANGELOG.md if applicable.

- [ ] I've added tests applicable for this pull request

What does this Pull Request accomplish?

Update version of releases/1.5 branch to 1.5.0.
Update installer_metadata.json in this PR on the releases/1.5 branch.

Why should this Pull Request be merged?

Prepare for nidaqmx-python 1.5 release.

What testing has been done?

image

@TanYiQing TanYiQing marked this pull request as ready for review April 22, 2026 05:30
@TanYiQing
Copy link
Copy Markdown
Collaborator Author

TanYiQing commented Apr 22, 2026

I also updated installer_metadata.json in this PR on the releases/1.5 branch. Yes, this is duplicate work, but the change is simple.
CONTRIBUTING.md:
Changes that only apply to the imminent release (such as version numbers) may be made directly in the release branch.

@github-actions
Copy link
Copy Markdown
Contributor

Test Results

    48 files  ±0      48 suites  ±0   1h 17m 52s ⏱️ +8s
 3 209 tests ±0   2 556 ✅ ±0     653 💤 ±0  0 ❌ ±0 
62 228 runs  ±0  49 398 ✅ ±0  12 830 💤 ±0  0 ❌ ±0 

Results for commit 7f4ca7b. ± Comparison against base commit db84f8d.

@bkeryan
Copy link
Copy Markdown
Collaborator

bkeryan commented Apr 22, 2026

I also updated installer_metadata.json in this PR on the releases/1.5 branch. Yes, this is duplicate work, but the change is simple. CONTRIBUTING.md: Changes that only apply to the imminent release (such as version numbers) may be made directly in the release branch.

Add it to the PR description.

BTW, the way we do this in AzDO is to merge into main and then cherry-pick, so why not do that in GitHub?

@TanYiQing
Copy link
Copy Markdown
Collaborator Author

I also updated installer_metadata.json in this PR on the releases/1.5 branch. Yes, this is duplicate work, but the change is simple. CONTRIBUTING.md: Changes that only apply to the imminent release (such as version numbers) may be made directly in the release branch.

Add it to the PR description.

BTW, the way we do this in AzDO is to merge into main and then cherry-pick, so why not do that in GitHub?

My intention in doing this is to save time during the review process. In my view, it should be acceptable for simple changes, though I agree it may not be appropriate for larger or more complex updates.

@TanYiQing TanYiQing merged commit 1651fab into releases/1.5 Apr 23, 2026
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants