[PR] optimize: restore Snap.svg header and stop RC Docker publish [incubator-seata]

Thu, 17 Sep 2026 06:52:15 -0700 


Bughue opened a new pull request, #8227:
URL: https://github.com/apache/incubator-seata/pull/8227

   ## Summary
   - Restore the Snap.svg / Adobe header on `PathMap.js` (remove the ASF 
stamp), ignore it in `.licenserc.yaml`, and copy the Snap.svg NOTICE first line 
into this project's NOTICE. This is the IPMC Round2 binding -1 on third-party 
code.
   - Point `babel-plugin-macros` in the binary LICENSE at 
`licenses/babel-plugin-macros-MIT` instead of emotion's MIT file.
   - Drop Apache License 2.0 grant text from `distribution/NOTICE*` 
(fastjson-1.2.83, context-propagation, micrometer jars) and keep copyright / 
attribution only.
   - Stop `publish-docker.yml` from publishing official tags / `latest` on 
every `*.*.*` branch push. Snapshot images stay on `snapshot` / `2.x`. Official 
tags are `workflow_dispatch` only, after the vote passes.
   
   Docker Hub cleanup of the already-pushed 2.7.0 tags is intentionally not in 
this PR.
   
   ## Test plan
   - [ ] Confirm `PathMap.js` no longer starts with an ASF header and 
`.licenserc.yaml` ignores it
   - [ ] Confirm root and `distribution/NOTICE` mention Snap.svg
   - [ ] Confirm `distribution/LICENSE` maps babel-plugin-macros to 
`babel-plugin-macros-MIT`
   - [ ] Confirm `distribution/NOTICE*` no longer embed `Licensed under the 
Apache License, Version 2.0` grant blocks
   - [ ] Confirm merging this PR into `2.7.0` does **not** run 
`-Prelease-image` (workflow no longer triggers on version-branch push)
   - [ ] After IPMC pass, publish official images with workflow_dispatch 
`publish_release=true`
   
   
   Made with [Cursor](https://cursor.com)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to