Skip to content

Bump sources + add g++ to Dockerfile + update CHANGELOGs for 26.06 release#461

Merged
puneetmatharu merged 1 commit into
ARM-software:mainfrom
puneetmatharu:bump-sources-for-26.06
May 29, 2026
Merged

Bump sources + add g++ to Dockerfile + update CHANGELOGs for 26.06 release#461
puneetmatharu merged 1 commit into
ARM-software:mainfrom
puneetmatharu:bump-sources-for-26.06

Conversation

@puneetmatharu
Copy link
Copy Markdown
Contributor

@puneetmatharu puneetmatharu commented May 28, 2026

Only worthy thing of note in this is that PyTorch removed the third_party/build_bundled.py script in pytorch/pytorch#180237 to create an updated bundled license.

@puneetmatharu puneetmatharu requested a review from nSircombe May 28, 2026 13:51
@puneetmatharu puneetmatharu force-pushed the bump-sources-for-26.06 branch from e4699f4 to 7428874 Compare May 28, 2026 15:01
nSircombe
nSircombe previously approved these changes May 28, 2026
Copy link
Copy Markdown
Contributor

@nSircombe nSircombe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...this is a very long way out to be putting a 'release' date in the CHANGELOG.mds, it's normally only a few days before the actual release.
I don't think it's ideal, as it looks a little bit like the release exists. Which it doesn't.

That said, it's not a blocker, and I don't think this will be the norm.

@puneetmatharu
Copy link
Copy Markdown
Contributor Author

...this is a very long way out to be putting a 'release' date in the CHANGELOG.mds, it's normally only a few days before the actual release.

It's normally done at the start of the release process and I'm off for a week before then so there's two weeks to handle the rest of the admin which is why I've done it now. Would you prefer I remove the name for now and actually wait until the week before to add it? Happy to do that and update our process.

@puneetmatharu puneetmatharu force-pushed the bump-sources-for-26.06 branch from 2ce46a2 to 1000cfe Compare May 28, 2026 19:01
@puneetmatharu
Copy link
Copy Markdown
Contributor Author

A unit test failed and it appears to be due to a torch.compile failure which stems from not having g++ in the final image. The test for this was added a couple of weeks ago to test_transformers.py (see PR). Since this is functionality that we should support, I've opted to install g++ in the image rather than skipping the test. It'll have a knock-on effect for the SBOM but one we'll just have to accept.

@nSircombe
Copy link
Copy Markdown
Contributor

...this is a very long way out to be putting a 'release' date in the CHANGELOG.mds, it's normally only a few days before the actual release.

It's normally done at the start of the release process and I'm off for a week before then so there's two weeks to handle the rest of the admin which is why I've done it now. Would you prefer I remove the name for now and actually wait until the week before to add it? Happy to do that and update our process.

I think it's ok. Just looks a bit odd, but under the circumstances I don't think we should sweat it.

Copy link
Copy Markdown
Contributor

@nSircombe nSircombe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From what I remember of the early SBOM work, the g++ licences won't present any big problems.

@puneetmatharu
Copy link
Copy Markdown
Contributor Author

Agreed, I think they'll be covered by the GNU GPL v3 license

@puneetmatharu puneetmatharu merged commit fa421d2 into ARM-software:main May 29, 2026
10 checks passed
@puneetmatharu puneetmatharu deleted the bump-sources-for-26.06 branch May 29, 2026 07:15
@puneetmatharu puneetmatharu changed the title Bump sources + update CHANGELOGs for 26.06 release Bump sources + add g++ to Dockerfile + update CHANGELOGs for 26.06 release May 29, 2026
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.

2 participants