Skip to content

Release by 18.03.2026#2611

Merged
Yakutoc merged 65 commits intomasterfrom
release_2025-03-18
Mar 18, 2026
Merged

Release by 18.03.2026#2611
Yakutoc merged 65 commits intomasterfrom
release_2025-03-18

Conversation

@Yakutoc
Copy link
Copy Markdown
Collaborator

@Yakutoc Yakutoc commented Mar 17, 2026

Core

TextField

  • расширены примеры документации

PR

NumberInput

  • добавлено свойство displayWithoutValue для отображения компонента без значения

  • добавлено свойство limitBehavior для управления поведением кнопок при достижении граничных значений

PR

Sheet

  • добавлена функция cleanup для корректной работы с глобальным body.style.overflowY

PR

Price

  • расширили type для свойства currency до string, что бы можно было указать валидное значение из ISO 4217 (а не только из предустановленного списка)

PR

Attach

  • добавлен аргумент для callback onClear

PR

Popover

  • улучшены примеры документации

  • добавлен пример как избежать потерю скругления между компонентом и slot контейнером

  • добавлено наследование для border-radius на уровне popover.style

PR

SDDS-PLATFORM-AI

Rating, DateTimePicker, DatePicker

  • добавлены в поставку

PR

PLASMA-GIGA

Theme

  • изменено значение для токена SurfaceDefaultCard

PR

SDDS-CS

Button, IconButton

  • исправлен токен для buttonBackground на surface-solid-secondary

PR

Build

  • убрана поставка styled-components. По умолчанию стала emotion;

PR

Yakutoc and others added 30 commits March 5, 2026 16:59
# Conflicts:
#	packages/plasma-asdk/package.json
@Yakutoc Yakutoc requested a review from IgorYar March 17, 2026 13:14
@Yakutoc Yakutoc changed the title Release by 17.03.2026 Release by 18.03.2026 Mar 17, 2026
Comment on lines +12 to +125
name: Upload ${{ matrix.package_name }} MCP data
if: ${{ github.event_name == 'workflow_dispatch' || github.event.workflow_run.conclusion == 'success' }}
runs-on: ubuntu-22.04
strategy:
fail-fast: false
matrix:
include:
- package_name: plasma-web
- package_name: plasma-b2c
- package_name: plasma-giga
- package_name: sdds-finai
steps:
- name: Checkout manual ref
if: ${{ github.event_name == 'workflow_dispatch' }}
uses: actions/checkout@v4
with:
show-progress: false

- name: Checkout release commit
if: ${{ github.event_name == 'workflow_run' }}
uses: actions/checkout@v4
with:
ref: ${{ github.event.workflow_run.head_sha }}
show-progress: false

- name: Prepare environment
uses: ./.github/actions/prepare-environment

- name: Read ${{ matrix.package_name }} version
run: |
PACKAGE_VERSION=$(node -p "require('./packages/${{ matrix.package_name }}/package.json').version")
echo "PACKAGE_VERSION=$PACKAGE_VERSION" >> $GITHUB_ENV
echo "S3_TARGET_VERSION_PATH=s3://${{ secrets.AWS_S3_BUCKET_2 }}/mcp/${{ matrix.package_name }}/$PACKAGE_VERSION/" >> $GITHUB_ENV
echo "S3_TARGET_LATEST_PATH=s3://${{ secrets.AWS_S3_BUCKET_2 }}/mcp/${{ matrix.package_name }}/latest/" >> $GITHUB_ENV

- name: Lerna bootstrap
uses: nick-fields/retry@v3
with:
timeout_minutes: 30
max_attempts: 2
retry_on: error
command: npx lerna bootstrap

- name: Build ${{ matrix.package_name }}-docs
env:
NODE_OPTIONS: "--max_old_space_size=10240"
run: npm run build --prefix="./website/${{ matrix.package_name }}-docs" -- --no-minify

- name: Generate index
run: npm run generate-index --prefix="./website/${{ matrix.package_name }}-docs"

- name: Generate MCP data
run: npm run generate-mcp-data --prefix="./website/${{ matrix.package_name }}-docs"

- name: Install s3cmd
run: pip3 install s3cmd

- name: Clean target S3 path
run: |
s3cmd \
--access_key ${{ secrets.AWS_ACCESS_KEY_ID }} \
--secret_key ${{ secrets.AWS_SECRET_ACCESS_KEY }} \
--host ${{ secrets.AWS_ENDPOINT }} \
--host-bucket ${{ secrets.AWS_ENDPOINT }} \
--bucket-location ${{ secrets.AWS_REGION }} \
--signature-v2 \
del \
--recursive \
--force \
${{ env.S3_TARGET_VERSION_PATH }}

- name: Upload MCP data to versioned s3 path
run: >
s3cmd
--access_key ${{ secrets.AWS_ACCESS_KEY_ID }}
--secret_key ${{ secrets.AWS_SECRET_ACCESS_KEY }}
--host ${{ secrets.AWS_ENDPOINT }}
--host-bucket ${{ secrets.AWS_ENDPOINT }}
--bucket-location ${{ secrets.AWS_REGION }}
--signature-v2
--delete-removed
--no-mime-magic
sync
./website/${{ matrix.package_name }}-docs/mcpData/
${{ env.S3_TARGET_VERSION_PATH }}

- name: Clean latest S3 path
run: |
s3cmd \
--access_key ${{ secrets.AWS_ACCESS_KEY_ID }} \
--secret_key ${{ secrets.AWS_SECRET_ACCESS_KEY }} \
--host ${{ secrets.AWS_ENDPOINT }} \
--host-bucket ${{ secrets.AWS_ENDPOINT }} \
--bucket-location ${{ secrets.AWS_REGION }} \
--signature-v2 \
del \
--recursive \
--force \
${{ env.S3_TARGET_LATEST_PATH }}

- name: Upload MCP data to latest s3 path
run: >
s3cmd
--access_key ${{ secrets.AWS_ACCESS_KEY_ID }}
--secret_key ${{ secrets.AWS_SECRET_ACCESS_KEY }}
--host ${{ secrets.AWS_ENDPOINT }}
--host-bucket ${{ secrets.AWS_ENDPOINT }}
--bucket-location ${{ secrets.AWS_REGION }}
--signature-v2
--delete-removed
--no-mime-magic
sync
./website/${{ matrix.package_name }}-docs/mcpData/
${{ env.S3_TARGET_LATEST_PATH }}

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}

Copilot Autofix

AI 24 days ago

In general, to fix this type of issue you explicitly define permissions: either at the workflow level (applies to all jobs) or for the specific job, limiting the GITHUB_TOKEN to the minimal scopes needed. For this workflow, the job only needs to read repository contents (for checkout); all deployment actions use AWS credentials via secrets and interact with S3 directly, not GitHub. So contents: read is sufficient and matches the minimal recommendation from CodeQL.

The best fix with no functional change is to add a permissions: block for the upload-mcp-data job (or at the workflow root). To keep the edit tightly scoped to the code shown, we’ll add it at the job level under upload-mcp-data:. Concretely, in .github/workflows/mcp-data-upload.yml, after line 12 (the job name:), insert:

        permissions:
            contents: read

with indentation matching the existing YAML structure (8 spaces before permissions and 12 before contents). No additional imports or methods are required since this is a configuration-only change.


Suggested changeset 1
.github/workflows/mcp-data-upload.yml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/mcp-data-upload.yml b/.github/workflows/mcp-data-upload.yml
--- a/.github/workflows/mcp-data-upload.yml
+++ b/.github/workflows/mcp-data-upload.yml
@@ -10,6 +10,8 @@
 jobs:
     upload-mcp-data:
         name: Upload ${{ matrix.package_name }} MCP data
+        permissions:
+            contents: read
         if: ${{ github.event_name == 'workflow_dispatch' || github.event.workflow_run.conclusion == 'success' }}
         runs-on: ubuntu-22.04
         strategy:
EOF
@@ -10,6 +10,8 @@
jobs:
upload-mcp-data:
name: Upload ${{ matrix.package_name }} MCP data
permissions:
contents: read
if: ${{ github.event_name == 'workflow_dispatch' || github.event.workflow_run.conclusion == 'success' }}
runs-on: ubuntu-22.04
strategy:
Copilot is powered by AI and may make mistakes. Always verify output.
Comment on lines +17 to +24
name: Release PLATFORM-AI next branch
if: github.ref == 'refs/heads/next-platform-ai'
uses: ./.github/workflows/publish-common.yml
with:
auto-options: '--no-changelog'
secrets:
gh_token: ${{ secrets.GH_TOKEN }}
npm_registry_token: ${{ secrets.NPM_REGISTRY_TOKEN }}

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {}

Copilot Autofix

AI 24 days ago

In general, the fix is to add an explicit permissions: block that grants only the minimal required scopes to the GITHUB_TOKEN. This can be done at the workflow root (applying to all jobs without their own permissions) or at the job level. Here, there is a single publish job that delegates to a reusable workflow; the safest non-breaking change is to define conservative permissions at the workflow root, which the reusable workflow can still narrow further if needed.

Concretely, in .github/workflows/publish-platform-ai.yml, add a permissions: block after the on: section (before concurrency:). As a minimal secure default for a release/publish workflow, use read-only repository access unless you know it must write to contents, deployments, etc. Since we must avoid assumptions about additional behavior, we will restrict to contents: read and packages: read, which aligns with GitHub’s recommended minimal starting point and does not introduce new functionality. If publish-common.yml needs broader rights, it should declare them explicitly itself. No imports or additional methods are needed; this is purely a YAML configuration change.

Suggested changeset 1
.github/workflows/publish-platform-ai.yml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/publish-platform-ai.yml b/.github/workflows/publish-platform-ai.yml
--- a/.github/workflows/publish-platform-ai.yml
+++ b/.github/workflows/publish-platform-ai.yml
@@ -8,6 +8,10 @@
           required: true
           default: 'next-platform-ai'
 
+permissions:
+  contents: read
+  packages: read
+
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true
EOF
@@ -8,6 +8,10 @@
required: true
default: 'next-platform-ai'

permissions:
contents: read
packages: read

concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
Copilot is powered by AI and may make mistakes. Always verify output.
Comment on lines +17 to +24
name: Release SBCOM next branch
if: github.ref == 'refs/heads/next-sbcom'
uses: ./.github/workflows/publish-common.yml
with:
auto-options: '--no-changelog'
secrets:
gh_token: ${{ secrets.GH_TOKEN }}
npm_registry_token: ${{ secrets.NPM_REGISTRY_TOKEN }}

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {}

Copilot Autofix

AI 24 days ago

To fix the problem, add an explicit permissions block so the GITHUB_TOKEN rights are constrained instead of inheriting potentially broad repository defaults. Since this workflow only dispatches a reusable workflow and does not itself interact with repository contents, a safe minimal starting point is contents: read. If the reusable workflow needs broader rights, those should be declared in that workflow; here we only need to ensure this caller workflow is not implicitly granting write access.

The single best change that preserves existing behavior is to add a root‑level permissions section near the top of .github/workflows/publish-sbcom.yml, after the name (or before on:), with least‑privilege read access to repo contents. Concretely, in .github/workflows/publish-sbcom.yml, insert:

permissions:
  contents: read

between line 2 and line 3. No imports or additional definitions are required, as this is purely a YAML configuration change.

Suggested changeset 1
.github/workflows/publish-sbcom.yml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/publish-sbcom.yml b/.github/workflows/publish-sbcom.yml
--- a/.github/workflows/publish-sbcom.yml
+++ b/.github/workflows/publish-sbcom.yml
@@ -1,5 +1,8 @@
 name: Release SBCOM next branch
 
+permissions:
+  contents: read
+
 on:
   workflow_dispatch:
     inputs:
EOF
@@ -1,5 +1,8 @@
name: Release SBCOM next branch

permissions:
contents: read

on:
workflow_dispatch:
inputs:
Copilot is powered by AI and may make mistakes. Always verify output.
@github-actions
Copy link
Copy Markdown
Contributor

Theme Builder app deployed!

https://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-2611/

@Yakutoc Yakutoc self-assigned this Mar 17, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Documentation preview deployed!

website: https://plasma.sberdevices.ru/pr/pr-2611/
web storybook: https://plasma.sberdevices.ru/pr/pr-2611/web-storybook/
b2c storybook: https://plasma.sberdevices.ru/pr/pr-2611/b2c-storybook/
ui storybook: https://plasma.sberdevices.ru/pr/pr-2611/ui-storybook/
new-hope storybook: https://plasma.sberdevices.ru/pr/pr-2611/new-hope-storybook/
asdk storybook: https://plasma.sberdevices.ru/pr/pr-2611/asdk-storybook/
giga storybook: https://plasma.sberdevices.ru/pr/pr-2611/giga-storybook/
homeds storybook: https://plasma.sberdevices.ru/pr/pr-2611/homeds-storybook/
sdds-serv storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-serv-storybook/
sdds-dfa storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-dfa-storybook/
sdds-cs storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-cs-storybook/
sdds-finai storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-finai-storybook/
sdds-insol storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-insol-storybook/
sdds-netology storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-netology-storybook/
sdds-scan storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-scan-storybook/
sdds-bizcom storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-bizcom-storybook/
sdds-platform-ai storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-platform-ai-storybook/
sdds-os storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-os-storybook/
sdds-sbcom storybook: https://plasma.sberdevices.ru/pr/pr-2611/sdds-sbcom-storybook/

@Yakutoc Yakutoc merged commit ddd447b into master Mar 18, 2026
48 checks passed
@Yakutoc Yakutoc deleted the release_2025-03-18 branch March 18, 2026 12:03
@Yakutoc Yakutoc mentioned this pull request Mar 31, 2026
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.

9 participants