fix(docs): use a plain year range in NOTICE copyright - #6983
Merged
Yicong-Huang merged 2 commits intoJul 29, 2026
Conversation
Per ASF policy, the NOTICE copyright line should use a plain year range, not "and onwards". Change to "Copyright 2025-2026 The Apache Software Foundation" in the root NOTICE and all */NOTICE-binary files. Closes apache#6981 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
xuang7
changed the title
Contributor
Automated Reviewer SuggestionsBased on the
|
github-actions
Bot
added
fix
docs
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6983 +/- ##
=========================================
Coverage 78.98% 78.98%
Complexity 3785 3785
=========================================
Files 1160 1160
Lines 46105 46105
Branches 5115 5115
=========================================
Hits 36414 36414
Misses 8069 8069
Partials 1622 1622
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Jul 29, 2026
Contributor
Yicong-Huang
pushed a commit
that referenced
this pull request
Jul 29, 2026
### What changes were proposed in this PR? Per ASF policy [1], the NOTICE copyright line should use a plain year range, not "and onwards". Changed `Copyright 2025 and onwards The Apache Software Foundation` to `Copyright 2025-2026 The Apache Software Foundation` in the root `NOTICE` and all `*/NOTICE-binary` files. [1] https://www.apache.org/legal/src-headers.html#notice ### Any related issues, documentation, discussions? Closes #6981. To be backported to `release/v1.2` for RC4. ### How was this PR tested? Text-only change; CI license/NOTICE checks pass with no generator drift. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) (backported from commit 1272137) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
xuang7
added a commit
that referenced
this pull request
Jul 29, 2026
### What changes were proposed in this PR? Automated backport of #6983 to `release/v1.2`. Source: 1272137 · [automation run](https://github.com/apache/texera/actions/runs/30423938766) ### Any related issues, documentation, discussions? Backport of #6983. Originally linked #6981. ### How was this PR tested? Release-branch CI runs on this branch once the conflicts are resolved and this PR is marked ready for review. ### Was this PR authored or co-authored using generative AI tooling? No. Co-authored-by: Xuan Gu <162244362+xuang7@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
renovate-bot
pushed a commit
to renovate-bot/apache-_-texera
that referenced
this pull request
Jul 29, 2026
…pache#7022) ### What changes were proposed in this PR? The `Report backport decisions` step in `backport-auto-label.yml` is skipped on every run, so the report comment and release-manager review request added in apache#6962 never fire. Root cause: the step's guard reads `steps.label.outputs.result`. `actions/github-script` always writes the script's return value to an output named `result` after the body runs. The `Label fix PRs` script has no `return`, so that post-run write blanks out the explicit `core.setOutput("result", …)` — the guard is therefore always false. Fix: rename the output to `decisions` (github-script only reserves `result`), and update the guard and the `RESULT` env reference to match. No logic in either step changes. ### Any related issues, documentation, discussions? Closes apache#7021. ### How was this PR tested? - Confirmed the failure on run `30423275226` (PR apache#7013): the `Report backport decisions` step shows `skipped`. - Verified 0 `<!-- backport-auto-label-report -->` comments across apache#7013, apache#6983, apache#6958, apache#6908 (including PRs that were auto-labeled), confirming the step is systemically skipped. - Change is name-only; the report/review logic is untouched, so it runs unchanged once the guard sees the output. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
Per ASF policy [1], the NOTICE copyright line should use a plain year
range, not "and onwards". Changed
Copyright 2025 and onwards The Apache Software FoundationtoCopyright 2025-2026 The Apache Software Foundationin the root
NOTICEand all*/NOTICE-binaryfiles.[1] https://www.apache.org/legal/src-headers.html#notice
Any related issues, documentation, discussions?
Closes #6981. To be backported to
release/v1.2for RC4.How was this PR tested?
Text-only change; CI license/NOTICE checks pass with no generator drift.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 4.8)