Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update manifest copyright date range #1603

Merged
merged 1 commit into from
Feb 28, 2025

Conversation

schrolla
Copy link
Collaborator

@schrolla schrolla commented Feb 27, 2025

🗣 Description

Update the ScubaGear module manifest copyright field to include the current year (2025).

💭 Motivation and context

Closes #1602

🧪 Testing

Review manifest file to see that it shows the copyright string date range is 2022-2025.
Publish test PSGallery module package and view its PSGallery page to see that the copyright statement reflects the updated version.

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • PR targets the correct parent branch (e.g., main or release-name) for merge.
  • Changes are limited to a single goal - eschew scope creep!
  • Changes are sized such that they do not touch excessive number of files.
  • All future TODOs are captured in issues, which are referenced in code comments.
  • These code changes follow the ScubaGear content style guide.
  • Related issues these changes resolve are linked preferably via closing keywords.
  • All relevant type-of-change labels added.
  • All relevant project fields are set.
  • All relevant repo and/or project documentation updated to reflect these changes.
  • Unit tests added/updated to cover PowerShell and Rego changes.
  • Functional tests added/updated to cover PowerShell and Rego changes.
  • All relevant functional tests passed.
  • All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

  • PR passed smoke test check.

  • Feature branch has been rebased against changes from parent branch, as needed

    Use Rebase branch button below or use this reference to rebase from the command line.

  • Resolved all merge conflicts on branch

  • Notified merge coordinator that PR is ready for merge via comment mention

  • Demonstrate changes to the team for questions and comments.
    (Note: Only required for issues of size Medium or larger)

✅ Post-merge checklist

  • Feature branch deleted after merge to clean up repository.
  • Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

@schrolla schrolla added the enhancement This issue or pull request will add new or improve existing functionality label Feb 27, 2025
@schrolla schrolla added this to the Marlin milestone Feb 27, 2025
@schrolla schrolla self-assigned this Feb 27, 2025
@schrolla schrolla linked an issue Feb 27, 2025 that may be closed by this pull request
1 task
@schrolla schrolla marked this pull request as ready for review February 27, 2025 22:17
@nanda-katikaneni nanda-katikaneni merged commit a3cb26c into main Feb 28, 2025
23 checks passed
@nanda-katikaneni nanda-katikaneni deleted the 1602-update-copyright-statement branch February 28, 2025 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This issue or pull request will add new or improve existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update copyright statement
3 participants