chore: release 1.0.0

Author: florentmaitre

.github/CONTRIBUTING.md

@@ -4,23 +4,31 @@ Looking to contribute something to OUDS Android? **Here's how you can help.**
 
 Please take a moment to review this document in order to make the contribution process easy for everyone involved.
 
-Following these guidelines helps to communicate that you respect the time of the developers managing and developing this Open Source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
+Following these guidelines helps to communicate that you respect the time of the developers managing and developing this Open Source project. In return, they
+should reciprocate that respect in addressing your issue or assessing patches and features.
 
 ## Using the Issue Tracker
 
-The [issue tracker](https://github.com/Orange-OpenSource/ouds-android/issues) is the preferred channel for [bug reports](#bug-reports), [feature requests](#feature-requests) and [submitting pull requests](#pull-requests), but please respect the following restrictions:
+The [issue tracker](https://github.com/Orange-OpenSource/ouds-android/issues) is the preferred channel
+for [bug reports](#bug-reports), [feature requests](#feature-requests) and [submitting pull requests](#pull-requests), but please respect the following
+restrictions:
 
-- Please **do not** use the issue tracker for personal support requests. [GitHub Discussions](https://github.com/Orange-OpenSource/ouds-android/discussions/categories/q-a) or our internal Orange communication tools are better places to get help.
+- Please **do not** use the issue tracker for personal support
+  requests. [GitHub Discussions](https://github.com/Orange-OpenSource/ouds-android/discussions/categories/q-a) or our internal Orange communication tools are
+  better places to get help.
 
 - Please **do not** derail or troll issues. Keep the discussion on topic and respect the opinions of others.
 
-- Please **do not** post comments consisting solely of "+1" or ":thumbsup:". Use [GitHub's "reactions" feature](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) instead. We reserve the right to delete comments which violate this rule.
+- Please **do not** post comments consisting solely of "+1" or ":thumbsup:".
+  Use [GitHub's "reactions" feature](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) instead. We reserve the right to
+  delete comments which violate this rule.
 
 ## Issues and Labels
 
 Our bug tracker utilizes several labels to help organize and identify issues. Here's what they represent and how we use them:
 
-- `feature` - Issues asking for a new feature to be added, or an existing one to be extended or modified. New features require a minor version bump (e.g., `v1.0.0` to `v1.1.0`).
+- `feature` - Issues asking for a new feature to be added, or an existing one to be extended or modified. New features require a minor version bump (e.g.,
+  `v1.0.0` to `v1.1.0`).
 - `help wanted` - Issues we need or would love help from the community to resolve.
 
 For a complete look at our labels, see the [project labels page](https://github.com/Orange-OpenSource/ouds-android/labels).
@@ -37,7 +45,9 @@ Guidelines for bug reports:
 
 3. **Isolate the problem** — ideally create a reduced reproducible test case.
 
-A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What device(s) and OS experience the problem? Do other devices show the bug differently? What would you expect to be the outcome? All these details will help people to fix any potential bugs.
+A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your
+environment? What steps will reproduce the issue? What device(s) and OS experience the problem? Do other devices show the bug differently? What would you expect
+to be the outcome? All these details will help people to fix any potential bugs.
 
 Example:
 
@@ -59,15 +69,19 @@ Example:
 
 ## Feature Requests
 
-Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to _you_ to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
+Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to _you_ to make a strong
+case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
 
 ## Pull requests
 
 Good pull requests—patches, improvements, new features—are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
 
-**Please ask first** before embarking on any **significant** pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project. For trivial things, or things that don't require a lot of your time, you can go ahead and make a PR.
+**Please ask first** before embarking on any **significant** pull request (e.g., implementing features, refactoring code, porting to a different language),
+otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project. For trivial things, or
+things that don't require a lot of your time, you can go ahead and make a PR.
 
-Please adhere to the [coding guidelines](#code-guidelines) used throughout the project (indentation, accurate comments, etc.) and any other requirements (such as test coverage).
+Please adhere to the [coding guidelines](#code-guidelines) used throughout the project (indentation, accurate comments, etc.) and any other requirements (such
+as test coverage).
 
 Adhering to the following process is the best way to get your work included in the project:
 
@@ -95,7 +109,8 @@ Adhering to the following process is the best way to get your work included in t
    git checkout -b <topic-branch-name>
    ```
 
-4. Commit your changes in logical chunks. Use Git's [interactive rebase](https://help.github.com/articles/about-git-rebase/) feature to tidy up your commits before making them public.
+4. Commit your changes in logical chunks. Use Git's [interactive rebase](https://help.github.com/articles/about-git-rebase/) feature to tidy up your commits
+   before making them public.
 
 5. Locally merge (or rebase) the upstream development branch into your topic branch:
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -56,7 +56,7 @@ _Note: Please transform `- [ ]` into `- (NA)` in the description when things are
 
 ### Checklist (for Core Team only)
 
-- [ ] Manually test (dark mode, RTL, landscape display, tablet)
+- [ ] Manually test (Dark mode, RTL, landscape display, tablet)
 - [ ] Documentation has been updated if relevant
 - [ ] Design review
 - [ ] A11y review

.github/workflows/app-distribution-alpha.yml

@@ -9,7 +9,7 @@ jobs:
     if: github.ref != 'refs/heads/main' && github.ref != 'refs/heads/develop'
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
 

.github/workflows/app-distribution-beta.yml

@@ -11,7 +11,7 @@ jobs:
     if: github.repository == 'Orange-OpenSource/ouds-android'
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
 

.github/workflows/build-docs.yml

@@ -20,15 +20,15 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
 
       - name: Build documentation with Dokka
         run: ./gradlew dokkaGenerate
 
       - name: Upload documentation artifacts
-        uses: actions/upload-artifact@v5
+        uses: actions/upload-artifact@v6
         with:
           name: docs
           path: docs/dokka
@@ -46,7 +46,7 @@ jobs:
       id-token: write   # to verify the deployment originates from an appropriate source
     steps:
       - name: Download artifacts
-        uses: actions/download-artifact@v6
+        uses: actions/download-artifact@v7
         with:
           name: docs
           path: docs
@@ -72,7 +72,7 @@ jobs:
     if: github.event_name != 'push' || github.ref != 'refs/heads/main'
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
           submodules: recursive
@@ -84,7 +84,7 @@ jobs:
           java-version: '17'
 
       - name: Download artifacts
-        uses: actions/download-artifact@v6
+        uses: actions/download-artifact@v7
         with:
           name: docs
           path: docs

.github/workflows/build.yml

@@ -19,7 +19,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
 
@@ -66,7 +66,7 @@ jobs:
 
       - name: Upload tests artifacts
         if: always()
-        uses: actions/upload-artifact@v5
+        uses: actions/upload-artifact@v6
         with:
           name: tests
           path: |
@@ -76,7 +76,7 @@ jobs:
             core/build/reports/tests
 
       - name: Upload app artifacts
-        uses: actions/upload-artifact@v5
+        uses: actions/upload-artifact@v6
         with:
           name: app
           path: app/build/outputs/apk/*/*/*.apk
@@ -90,7 +90,7 @@ jobs:
       url: https://mvnrepository.com/artifact/com.orange.ouds.android
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
           submodules: recursive
@@ -128,7 +128,7 @@ jobs:
       url: https://github.com/Orange-OpenSource/ouds-android/releases
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
           submodules: recursive
@@ -161,7 +161,7 @@ jobs:
       url: https://play.google.com/store/apps
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
           submodules: recursive
@@ -178,7 +178,7 @@ jobs:
           curl -F 'file=@app/build/outputs/bundle/prodRelease/app-prod-release.aab' https://oma-portal.orange.fr/oma/api/v1/external/applications/${{ secrets.OMA_APP_ID }}/artifacts -H "apiKey:${{ secrets.OMA_APP_TOKEN }}"
 
       - name: Store Google Play Store artifacts
-        uses: actions/upload-artifact@v5
+        uses: actions/upload-artifact@v6
         with:
           name: google-play-store
           path: |

CHANGELOG.md

@@ -5,6 +5,41 @@ All notable changes done in OUDS Android library will be documented in this file
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.0](https://github.com/Orange-OpenSource/ouds-android/compare/0.4.0...1.0.0) (2025-12-18)
+
+### Features
+
+- **button** remove background for minimal buttons in loading state ([#995](https://github.com/Orange-OpenSource/ouds-android/issues/995))
+- **checkbox-item** **radio-button-item** **switch-item** **text-input** add a constrained max width parameter to these components ([#985](https://github.com/Orange-OpenSource/ouds-android/issues/985))
+- create component - top app bar ([#954](https://github.com/Orange-OpenSource/ouds-android/issues/954))
+- update OUDS icons to 1.4 and change the structure to access to icons drawable resources ([#974](https://github.com/Orange-OpenSource/ouds-android/issues/974))
+- **checkbox-item** **radio-button-item** **switch-item** Update edge-to-edge padding management on control items  ([#939](https://github.com/Orange-OpenSource/ouds-android/issues/939))
+- **checkbox-item** **radio-button-item** **switch-item** update to switch 1.5, checkbox v2.4 and radio button 1.4 ([#922](https://github.com/Orange-OpenSource/ouds-android/issues/922))
+- **checkbox-item** **radio-button-item** **switch-item** update design of OudsCheckboxItem to 2.3, OudsRadioButtonItem to 1.3 and OudsSwitchItem to 1.4 ([#896](https://github.com/Orange-OpenSource/ouds-android/issues/896))
+- create component - navigation bar ([#631](https://github.com/Orange-OpenSource/ouds-android/issues/631))
+
+### Bug Fixes
+
+- **deps** update dependency org.mockito:mockito-android to v5.21.0 ([#988](https://github.com/Orange-OpenSource/ouds-android/issues/988))
+- **deps** update gradle to v8.13.2 ([#989](https://github.com/Orange-OpenSource/ouds-android/issues/989))
+- **tag** scale functional icons and loader for a11y reasons ([#960](https://github.com/Orange-OpenSource/ouds-android/issues/960))
+- **deps** update dependency com.google.auth:google-auth-library-oauth2-http to v1.41.0 ([#972](https://github.com/Orange-OpenSource/ouds-android/issues/972))
+- **deps** update dependency androidx.compose:compose-bom to v2025.12.00 ([#971](https://github.com/Orange-OpenSource/ouds-android/issues/971))
+- **deps** update dependency androidx.activity:activity-compose to v1.12.1 ([#970](https://github.com/Orange-OpenSource/ouds-android/issues/970))
+- apply missing tokens to control item component
+- **deps** update dependency dev.chrisbanes.haze:haze to v1.7.1 ([#956](https://github.com/Orange-OpenSource/ouds-android/issues/956))
+- demo app crashes when scrolling through color tokens with orange theme ([#953](https://github.com/Orange-OpenSource/ouds-android/issues/953))
+- **deps** update dependency dev.chrisbanes.haze:haze to v1.7.0 ([#949](https://github.com/Orange-OpenSource/ouds-android/issues/949))
+- **deps** update dependency androidx.compose:compose-bom to v2025.11.01 ([#941](https://github.com/Orange-OpenSource/ouds-android/issues/941))
+- **deps** update dependency androidx.activity:activity-compose to v1.12.0 ([#942](https://github.com/Orange-OpenSource/ouds-android/issues/942))
+- **deps** update dependency androidx.datastore:datastore-preferences to v1.2.0 ([#943](https://github.com/Orange-OpenSource/ouds-android/issues/943))
+- **deps** update grpc-java monorepo to v1.77.0 ([#936](https://github.com/Orange-OpenSource/ouds-android/issues/936))
+- **deps** update zxing to v3.5.4 ([#927](https://github.com/Orange-OpenSource/ouds-android/issues/927))
+- **deps** update gradle to v8.13.1 ([#919](https://github.com/Orange-OpenSource/ouds-android/issues/919))
+- **a11y** **text-input** error description is heard twice with Talkback ([#913](https://github.com/Orange-OpenSource/ouds-android/issues/913))
+- **deps** update dependency androidx.compose:compose-bom to v2025.11.00 ([#906](https://github.com/Orange-OpenSource/ouds-android/issues/906))
+- **deps** update dependency androidx.navigation:navigation-compose to v2.9.6 ([#905](https://github.com/Orange-OpenSource/ouds-android/issues/905))
+
 ## [0.4.0](https://github.com/Orange-OpenSource/ouds-android/compare/0.3.0...0.4.0) (2025-11-06)
 
 ### Features