Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
GÉANT Service Orchestrator
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GÉANT Orchestration and Automation Team
GAP
GÉANT Service Orchestrator
Commits
98e65bd6
Commit
98e65bd6
authored
9 months ago
by
geant-release-service
Browse files
Options
Downloads
Plain Diff
Finished release 2.36.
parents
b78bbcf4
20c94251
No related branches found
No related tags found
No related merge requests found
Pipeline
#91854
passed
9 months ago
Stage: tox
Stage: documentation
Stage: sonarqube
Stage: trigger_jenkins_build
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
Changelog.md
+8
-0
8 additions, 0 deletions
Changelog.md
with
8 additions
and
0 deletions
Changelog.md
+
8
−
0
View file @
98e65bd6
# Changelog
## [2.36] - 2025-02-11
-
Make use of already available app_settings instead of calling os environment
-
Hotfix sharepoint interaction (2 attempts)
-
Use shared_task instead of celery decorator
-
Use externally defined lists for L3 Core and layer 2 circuit service types to avoid unit tests falling out of sync
-
Add bulk migration for an edge port
-
Add L3 Core Service migration
## [2.35] - 2025-01-30
-
Fix a bug in the L3 Core Service validation workflow
...
...
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment