Skip to content

Commit 2d826b7

Browse files
committed
chore: split migration file out for 26.03 (Sofie-Automation#1683)
1 parent 8986328 commit 2d826b7

5 files changed

Lines changed: 10 additions & 18 deletions

File tree

Lines changed: 5 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
import { addMigrationSteps } from './databaseMigration'
2-
import { CURRENT_SYSTEM_VERSION } from './currentSystemVersion'
32
import { MongoInternals } from 'meteor/mongo'
43
import { Studios } from '../collections'
54
import { ExpectedPackages } from '../collections'
@@ -11,17 +10,9 @@ import {
1110
import { BucketId, RundownId } from '@sofie-automation/corelib/dist/dataModel/Ids'
1211
import { assertNever, Complete } from '@sofie-automation/corelib/dist/lib'
1312

14-
/*
15-
* **************************************************************************************
16-
*
17-
* These migrations are destined for the next release
18-
*
19-
* (This file is to be renamed to the correct version number when doing the release)
20-
*
21-
* **************************************************************************************
22-
*/
13+
// Release 26.03 (aka Release 53)
2314

24-
export const addSteps = addMigrationSteps(CURRENT_SYSTEM_VERSION, [
15+
export const addSteps = addMigrationSteps('26.3.0', [
2516
{
2617
id: `Drop media manager collections`,
2718
canBeRunAutomatically: true,
@@ -36,7 +27,9 @@ export const addSteps = addMigrationSteps(CURRENT_SYSTEM_VERSION, [
3627
['expectedMediaItems', 'mediaWorkFlows', 'mediaWorkFlowSteps'].includes(c.name)
3728
)
3829
if (collectionsToDrop.length > 0) {
39-
return `There are ${collectionsToDrop.length} obsolete collections to be removed: ${collectionsToDrop.map((c) => c.name).join(', ')}`
30+
return `There are ${collectionsToDrop.length} obsolete collections to be removed: ${collectionsToDrop
31+
.map((c) => c.name)
32+
.join(', ')}`
4033
}
4134

4235
return false

meteor/server/migration/currentSystemVersion.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,4 +55,4 @@
5555
*/
5656

5757
// Note: Only set this to release versions, (ie X.Y.Z), not pre-releases (ie X.Y.Z-0-pre-release)
58-
export const CURRENT_SYSTEM_VERSION = '1.53.0'
58+
export const CURRENT_SYSTEM_VERSION = '26.3.0'

meteor/server/migration/migrations.ts

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,5 @@ addSteps1_51_0()
4040
import { addSteps as addSteps1_52_0 } from './1_52_0'
4141
addSteps1_52_0()
4242

43-
// Migrations for the in-development release:
44-
import { addSteps as addStepsX_X_X } from './X_X_X'
45-
addStepsX_X_X()
43+
import { addSteps as addSteps26_03 } from './26_03'
44+
addSteps26_03()

packages/documentation/docs/for-developers/device-integrations/tsr-plugins.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# TSR Plugins
22

3-
As of 1.53, it is possible to load additional device integrations into TSR as 'plugins'. This is intended to be an escape hatch when you need to make an integration for an internal system or for when an NDA with a device vendor does not allow for opensourcing. We still encourage anything which can be made opensource to be contributed back.
3+
As of 26.03, it is possible to load additional device integrations into TSR as 'plugins'. This is intended to be an escape hatch when you need to make an integration for an internal system or for when an NDA with a device vendor does not allow for opensourcing. We still encourage anything which can be made opensource to be contributed back.
44

55
## Creating a plugin
66

packages/documentation/versioned_docs/version-26.03.0/for-developers/device-integrations/tsr-plugins.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# TSR Plugins
22

3-
As of 1.53, it is possible to load additional device integrations into TSR as 'plugins'. This is intended to be an escape hatch when you need to make an integration for an internal system or for when an NDA with a device vendor does not allow for opensourcing. We still encourage anything which can be made opensource to be contributed back.
3+
As of 26.03, it is possible to load additional device integrations into TSR as 'plugins'. This is intended to be an escape hatch when you need to make an integration for an internal system or for when an NDA with a device vendor does not allow for opensourcing. We still encourage anything which can be made opensource to be contributed back.
44

55
## Creating a plugin
66

0 commit comments

Comments
 (0)