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

chore: Update Uno #423

Merged
merged 1 commit into from
Jan 28, 2025
Merged

chore: Update Uno #423

merged 1 commit into from
Jan 28, 2025

Conversation

Soap-141
Copy link
Contributor

@Soap-141 Soap-141 commented Jan 22, 2025

GitHub Issue: #

Proposed Changes

  • Bug fix
  • Feature
  • Code style update (formatting)
  • Refactoring (no functional changes, no api changes)
  • Build or CI related changes
  • Documentation content changes
  • Other, please describe:

Description

Update Uno packages to the latest version.

Impact on version

  • Major
    • The template structure was changed.
  • Minor
    • New functionalities were added.
  • Patch
    • A bug in behavior was fixed.
    • Documentation was changed.

PR Checklist

Always applicable

No matter your changes, these checks always apply.

  • Your conventional commits are aligned with the Impact on version section.
  • Updated CHANGELOG.md.
    • Use the latest Major.Minor.X header if you do a Patch change.
    • Create a new Major.Minor.X header if you do a Minor or Major change.
    • If you create a new header, it aligns with the Impact on version section and matches what is generated in the build pipeline.
  • Documentation files were updated according with the changes.
    • Update README.md and TemplateConfig.md if you made changes to templating.
    • Update AzurePipelines.md and APP_README.md if you made changes to pipelines.
    • Update Diagnostics.md if you made changes to diagnostic tools.
    • Update Architecture.md and its diagrams if you made architecture decisions or if you introduced new recipes.
    • ...and so forth: Make sure you update the documentation files associated to the recipes you changed. Review the topics by looking at the content of the doc/ folder.
  • Images about the template are referenced from the wiki and added as images in this git.
  • TODO comments are hints for next steps for users of the template and not planned work.

Contextual

Based on your changes these checks may not apply.

  • Automated tests for the changes have been added/updated.
  • Tested on all relevant platforms

Other information

Internal Issue (If applicable):

@Soap-141 Soap-141 force-pushed the dev/thla/feat-update-uno branch from f83c2cd to 0516870 Compare January 23, 2025 21:50
@Soap-141 Soap-141 changed the title Dev/thla/feat update uno feat: Uno Update Jan 23, 2025
@Soap-141 Soap-141 changed the title feat: Uno Update feat: Update Uno Jan 23, 2025
@Soap-141 Soap-141 force-pushed the dev/thla/feat-update-uno branch 5 times, most recently from 67c7c5b to 37cbd74 Compare January 24, 2025 16:21
@Soap-141 Soap-141 marked this pull request as ready for review January 24, 2025 16:22
@Soap-141 Soap-141 force-pushed the dev/thla/feat-update-uno branch from 37cbd74 to 0b06b41 Compare January 28, 2025 21:03
@Soap-141 Soap-141 changed the base branch from main to feature/uno-update January 28, 2025 21:04
@Soap-141 Soap-141 changed the title feat: Update Uno chore: Update Uno Jan 28, 2025
@Soap-141 Soap-141 force-pushed the dev/thla/feat-update-uno branch from 0b06b41 to 4ae41dd Compare January 28, 2025 21:09
@Soap-141 Soap-141 force-pushed the dev/thla/feat-update-uno branch from b0873b7 to 0dbb18d Compare January 28, 2025 21:10
@Soap-141 Soap-141 merged commit 3e187cc into feature/uno-update Jan 28, 2025
15 checks passed
@Soap-141 Soap-141 deleted the dev/thla/feat-update-uno branch January 28, 2025 21:43
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