Skip to content

chore(deps): Bump Swashbuckle.AspNetCore from 7.2.0 to 10.2.1#98

Merged
JaviFRx merged 32 commits into
mainfrom
dependabot/nuget/src/NexusCad.Api/Swashbuckle.AspNetCore-10.2.1
Jun 3, 2026
Merged

chore(deps): Bump Swashbuckle.AspNetCore from 7.2.0 to 10.2.1#98
JaviFRx merged 32 commits into
mainfrom
dependabot/nuget/src/NexusCad.Api/Swashbuckle.AspNetCore-10.2.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jun 3, 2026

Updated Swashbuckle.AspNetCore from 7.2.0 to 10.2.1.

Release notes

Sourced from Swashbuckle.AspNetCore's releases.

10.2.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.0...v10.2.1

10.2.0

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.7...v10.2.0

10.1.7

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.6...v10.1.7

10.1.6

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.5...v10.1.6

10.1.5

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.4...v10.1.5

10.1.4

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.3...v10.1.4

10.1.3

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.2...v10.1.3

10.1.2

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.1...v10.1.2

10.1.1

What's Changed

New Contributors

Full Changelog:

domaindrivendev/Swashbuckle.AspNetCore@v10.1.0...v10.1.1

10.1.0

What's Changed

New Features

Bug Fixes

Miscellaneous

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.0.1...v10.1.0

10.0.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.0.0...v10.0.1

10.0.0

Swashbuckle.AspNetCore v10.0.0

[!IMPORTANT]
This release contains major breaking changes.

Read our v10 migration guide for further information.

With this release, Swashbuckle.AspNetCore adds support for generating OpenAPI 3.1 documents and for ASP.NET Core 10.

Swashbuckle.AspNetCore v10 depends on OpenAPI.NET v2.3 which introduces many breaking changes to the public API surface. More information can be found in their OpenAPI.NET v2 Upgrade Guide.

To reduce the number of breaking behavioural changes in Swashbuckle.AspNetCore v10, generation of OpenAPI 3.1 documents is opt-in.
To generate OpenAPI 3.1 documents, change the OpenAPI version as shown in the code snippet below:

app.UseSwagger(options =>
{
    options.OpenApiVersion = OpenApiSpecVersion.OpenApi3_1;
});

[!TIP]
It is strongly recommended that you upgrade to Swashbuckle.AspNetCore v9.0.6 before upgrading to v10.

[!IMPORTANT]
Use of Swashbuckle.AspNetCore with the ASP.NET Core WithOpenApi() method is no longer supported.

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.6...v10.0.0

9.0.6

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.5...v9.0.6

9.0.5

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.4...v9.0.5

9.0.4

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.3...v9.0.4

9.0.3

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.2...v9.0.3

9.0.2

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.1...v9.0.2

9.0.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.0...v9.0.1

9.0.0

📣 This release contains the following breaking changes:

  • Drops support for netstandard2.0 and thus .NET Framework - now only net8.0 and net9.0 are supported.
  • Removes all public members annotated as [Obsolete] in previous releases.
  • Removes the deprecated --serializeasv2 option from Swashbuckle.AspNetCore.Cli, which was superseded by --openapiversion from version 8.0.0.

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.4...v9.0.0

8.1.4

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.3...v8.1.4

8.1.3

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.2...v8.1.3

8.1.2

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.1...v8.1.2

8.1.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.0...v8.1.1

8.1.0

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.0.0...v8.1.0

8.0.0

[!IMPORTANT]
Swashbuckle.AspNetCore drops support for .NET 6.

Swashbuckle.AspNetCore v8.0.0 makes the following notable changes:

  • Drops support for net6.0.
  • The netstandard2.0 TFM now depends on ASP.NET Core 2.3 instead of ASP.NET Core 2.1.
  • Updates Microsoft.OpenApi to v1.6.23. This update requires the use of swagger-ui v5.19.0 or later (v5.20.1 is included in the Swashbuckle.AspNetCore.SwaggerUI NuGet package). You may need to clear your browser's cache to pick up the latest JavaScript files for swagger-ui.
  • To prepare for future support for OpenAPI 3.1 documents, deprecates the SerializeAsV2 property by marking it as [Obsolete]. Users should update their code as illustrated below, depending on their use case:
    - options.SerializeAsV2 = true;
    + options.OpenApiVersion = Microsoft.OpenApi.OpenApiSpecVersion.OpenApi2_0;
    
    // or if explicitly disabling (the same as the default behaviour)
    - options.SerializeAsV2 = false;
    + options.OpenApiVersion = Microsoft.OpenApi.OpenApiSpecVersion.OpenApi3_0;
  • To prepare for future support for OpenAPI 3.1 documents, the Swashbuckle.AspNetCore.Cli tool has deprecated the --serializeasv2 option and logs a warning to the console. Users should update their usage as illustrated below, depending on their use case:
    - swagger tofile --output [output] [startupassembly] [swaggerdoc] --serializeasv2
    + swagger tofile --output [output] [startupassembly] [swaggerdoc] --openapiversion "2.0"

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v7.3.2...v8.0.0

7.3.2

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v7.3.1...v7.3.2

7.3.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v7.3.0...v7.3.1

7.3.0

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v7.2.0...v7.3.0

Commits viewable in compare view.

JaviFRx and others added 20 commits May 28, 2026 10:46
VS rejected the prior <Configuration SolutionConfiguration=...
SolutionPlatform=...> form with "project configuration does not exist".
The vs-solutionpersistence parser requires Platform/BuildType elements
whose Solution attribute is a combined BuildType|Platform string.

Replace the two Configuration entries with a single canonical rule
mapping all solution build types under Any CPU to the SwAddIn's x64
project platform.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Create HomePage.tsx with hero banner, 4-step workflow, roles, and
  detailed sections for Capture, Admin, Web and SwWorker components
- Add /home route as root entry point (replaces /projects redirect)
- Add 'Inicio' nav button as first item in Header using HomeIcon
- Keep /dashboard route and stats page unchanged

Based on MANUAL.es.md content.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Create HomeView.xaml with hero banner, 4-step workflow, roles,
  Capture/Admin/SwWorker sections mirroring web HomePage
- Create HomeView.xaml.cs code-behind
- Wire 'Home' node in NavigateToNode switch so clicking Home in the
  navigation tree shows the documentation view instead of the placeholder

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Fix XamlParseException at runtime caused by invalid enum values in
PackIconMaterial Kind attributes. Replaced: SettingsOutlineCogOutline,
PuzzleOutlineApplicationCogOutline, TuneVerticalCog,
VectorSquareFileDocumentOutline, DownloadContentSaveOutline,
MemoryDatabaseSearchOutline, AlertOutlineAlertCircleOutline.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Call NavigateToNode('Home') at the end of InitializeAsync so the Home
documentation view is shown immediately when the app launches.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Introduce NexusCad.Core.Configuration.StorageOptions as the single
source of truth for all file system paths:

- RootPath (default C:\NexusCad) as base
- ModelsPath   master SolidWorks templates per project
- OutputPath   generated SW files (SLDPRT/SLDASM/SLDDRW) per job
- DocumentsPath  generated PDF/DOCX ready for download
- BundlesPath  Vite form bundles uploaded by \
exuscad push\
- TempPath     job working dirs (cleaned after completion)

All paths fall back to {RootPath}\{Name} if not set.
Helper methods: GetProjectModelsPath(code), GetJobOutputPath(id),
GetJobTempPath(id).

Wire-up:
- Registered in NexusCad.Api Program.cs (IOptions<StorageOptions>)
- Registered in NexusCad.SwWorker Program.cs (replaces WorkingDirectory)
- JobProcessor injected with StorageOptions; uses GetJobTempPath and
  GetProjectModelsPath instead of hardcoded C:\NexusCad\Jobs\Templates
- SolidWorksOptions.WorkingDirectory removed (replaced by StorageOptions)
- Storage section added to appsettings.json in both Api and SwWorker

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- SecuritySettingsView converted to TabControl with Users and Groups tabs
- Groups tab: DataGrid (Code, Name, Description, Created, Updated) + toolbar (New, Edit, Delete, Refresh)
- New Group: reuses existing NewGroupDialog
- Edit Group: new GroupEditDialog + GroupEditDialogViewModel (Name, Description, WorkspacePath, IconUrl)
- Delete Group: confirmation dialog, handles 409 Conflict when group has projects
- SecuritySettingsViewModel extended with group CRUD commands and state
- Both tabs load on DataContextChanged

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add admin section to the web app for managing user group memberships:

Backend:
- GET /api/auth/users/{id}/memberships  returns user's group memberships
- PUT /api/auth/users/{id}/memberships  replaces user's group memberships
- New DTOs: UserGroupMembershipDto, SetUserMembershipsRequest, UserMembershipItem

Frontend:
- /admin/users  user list page (table with roles, status, last login)
- /admin/users/:id  user edit page with two tabs:
  - 'Datos básicos': name, active switch, global roles (chips), optional new password
  - 'Acceso a grupos': checkbox table  select which groups the user
    can see and assign their role within each group (Owner/Author/Commercial/Client)
- AdminRoute guard: non-admin users redirected to /home
- Header: 'Administración' nav link visible only to Admin role users
- admin.service.ts: API calls for users and group memberships

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Each project can now specify its own SolidWorks master models folder.
Priority chain: Project.ModelsPath > Group.WorkspacePath > StorageOptions default.

Changes:
- Project entity: nullable ModelsPath property
- EF migration: AddProjectModelsPath
- API DTOs: ModelsPath on ProjectDto, CreateProjectRequest, UpdateProjectRequest
- ProjectsController: persist and return ModelsPath on all write endpoints
- Admin WPF ProjectDto / UpdateProjectRequest: add ModelsPath
- ProjectEditorViewModel: ModelsPath property + BrowseModelsPathCommand
  (FolderBrowserDialog via UseWindowsForms)
- ProjectEditorView.xaml: 'Ruta de modelos SolidWorks' field with Browse button
  inside Project Information card

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- TabControl with 'Datos básicos' and 'Acceso a grupos' tabs
- Role descriptions shown per role (Admin, Autor, Comercial, Cliente)
- Group membership tab: checkbox per group + role ComboBox (Owner/Autor/Comercial/Cliente)
- EditUser() loads current memberships before opening dialog
- EditUser() saves memberships after user confirms
- New UserGroupMembershipDto, SetUserMembershipsRequest, MembershipItem DTOs for WPF
- GetUserMembershipsAsync / SetUserMembershipsAsync added to INexusCadApi Refit interface

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
API endpoints (/api/groups) unchanged. Only internal naming updated:
- New Workspace* DTOs, service, ViewModels and Views
- SecuritySettingsViewModel/View updated to Workspace commands
- OpenProjectDialogViewModel updated to ICurrentWorkspaceService
- Old Group* files deleted

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…nd ref

- Remove <UseWindowsForms>true</UseWindowsForms> from .csproj (was causing
  WPF/WinForms type ambiguities: UserControl, Application, Point, Size, etc.)
- Replace System.Windows.Forms.FolderBrowserDialog with Microsoft.Win32.OpenFolderDialog
  in ProjectEditorViewModel.BrowseModelsPath()
- Fix SecuritySettingsView.xaml.cs: LoadGroupsCommand  LoadWorkspacesCommand
- Fix UserEditDialog.xaml.cs: move role var usage inside pattern match scope

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
After the GroupWorkspace rename, the persisted state file was named
active-group.json with property ActiveGroupId. The new code looks for
active-workspace.json with ActiveWorkspaceId, so the last active workspace
was not restored on startup  projects panel appeared empty.

LoadStoredIdAsync now auto-migrates: if active-workspace.json is missing
but active-group.json exists, it reads the legacy ActiveGroupId, writes
the new format, and deletes the old file transparently.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Migration body was empty  the ModelsPath column was never added to the
Projects table in SQLite. EF marked it as applied, so MigrateAsync()
skipped it on startup, causing a 500 on GET /api/projects (no such column).

Added the missing AddColumn/DropColumn operations. The column was added
directly to dev DB via ALTER TABLE as a hotfix.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- New GroupProjectAccess entity (GroupId, ProjectId, AccessLevel)
- ProjectAccessLevel enum: View=0, Configure=1
- API endpoints: GET/PUT /api/groups/{id}/project-access (Admin only)
- EF migration AddGroupProjectAccess applied
- WPF WorkspaceEditDialog: new Proyectos tab with checkbox+level per project
- WorkspaceEditDialogViewModel: WorkspaceProjectAccessItem observable class
- SecuritySettingsViewModel: load/save project access when editing workspace
- INexusCadApi: GetWorkspaceProjectAccessAsync + SetWorkspaceProjectAccessAsync

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
El servicio Windows no usa launchSettings.json, por lo que Kestrel
arrancaba en el puerto 5000 por defecto y el Admin (que apunta al 5140)
no podia conectar. Se fija Urls en appsettings.json.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Core: UserGroup + UserGroupMember entities, IUserGroupRepository
- Infrastructure: UserGroupRepository, AppDbContext mapping,
  migration 20260601074349_AddUserGroups
- API: UserGroupsController (GET/POST/PUT/DELETE + members set),
  DTOs, register IUserGroupRepository in Program.cs
- Admin WPF: GroupEditDialog (config + members tabs),
  GroupEditDialogViewModel, SecuritySettingsViewModel Groups tab,
  INexusCadApi endpoints, WorkspacesListChanged propagation
  to MainWindowViewModel sidebar
- Remove GroupRole enum usage from all controllers and DTOs
- Simplify GroupMembership to membership-only (no role column)
- Add UserGroupProjectAccess entity for per-group project visibility
- Remove role ComboBox from GroupEditDialog and UserEditDialog
- Reduce system roles to Admin only
- Add EF migration: AddUserGroupProjectAccess_RemoveMembershipRole
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Jun 3, 2026

Labels

The following labels could not be found: dependencies, dotnet. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot requested a review from JaviFRx as a code owner June 3, 2026 06:04
JaviFRx and others added 6 commits June 3, 2026 12:15
- Add GroupProjectItem class to GroupEditDialogViewModel
- Add ProjectItems collection to GroupEditDialogViewModel
- Add 'Proyectos' tab in GroupEditDialog.xaml with checkbox list
- Update GroupEditDialog.xaml.cs to handle NoProjectsText visibility
- Add GetUserGroupProjectsAsync/SetUserGroupProjectsAsync to INexusCadApi
- Add UserGroupProjectDto and SetUserGroupProjectsRequest to Admin.Models
- Load current project access when editing a group
- Save selected projects on confirm (create and edit flow)
---
updated-dependencies:
- dependency-name: Swashbuckle.AspNetCore
  dependency-version: 10.2.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/nuget/src/NexusCad.Api/Swashbuckle.AspNetCore-10.2.1 branch from b0e0c68 to 6808ec9 Compare June 3, 2026 11:24
- Created .vscode/launch.json with Chrome, Edge, and pnpm dev configurations
- Added web/Properties/launchSettings.json for Visual Studio deployment
- Configured correct port (3000) matching vite.config.ts settings
- Resolves 'El valor no puede ser nulo' deployment error
JaviFRx and others added 5 commits June 3, 2026 13:31
- Agregar LaunchCommand y LaunchUrl a NexusCad.Web.esproj
- Actualizar launchSettings.json con schema y configuración completa
- Crear script CleanVSCache.ps1 para limpiar caché de Visual Studio
- Agregar documentación de troubleshooting para VS2026
- Incluir perfiles de lanzamiento con inspectUri para depuración

Resolves: Error 'El valor no puede ser nulo. Nombre del parámetro: source'
Issue: Problema específico de VS2026 con proyectos esproj
- Remover .vscode/launch.json que causaba error 'source null'
- Eliminar LaunchCommand/LaunchUrl de NexusCad.Web.esproj
- Agregar ShouldRunBuildScript para compilación correcta
- Crear documentación SOLUCION-VS2026-ESPROJ.md

CAUSA RAÍZ: VS2026 no soporta 'Implementar/Deploy' en proyectos esproj.
SOLUCIÓN: Usar F5/Ctrl+F5 (Ejecutar) en lugar de 'Deploy'

Los proyectos JavaScript/TypeScript se ejecutan, no se implementan.
- INSTRUCCIONES-URGENTE.md: Guía paso a paso para NO usar Deploy
- RunWeb.ps1: Script para ejecutar el servidor de desarrollo directamente
- Énfasis en usar F5/Ctrl+F5 en lugar de Implementar/Deploy

El usuario continúa usando 'Implementar' que no funciona con esproj.
Necesita usar 'Depurar/Ejecutar' o terminal directamente.
Microsoft.OpenApi 2.x removed the `.Models` sub-namespace and replaced
`OpenApiReference` with typed reference classes. Update Swagger setup to
use `OpenApiSecuritySchemeReference` and the `Func<OpenApiDocument, ...>`
overload of `AddSecurityRequirement`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@JaviFRx JaviFRx merged commit c8dc335 into main Jun 3, 2026
9 checks passed
@JaviFRx JaviFRx deleted the dependabot/nuget/src/NexusCad.Api/Swashbuckle.AspNetCore-10.2.1 branch June 3, 2026 13:03
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.

1 participant