You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/maintainer/pinning_deps.rst
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,18 +104,18 @@ for the affected packages in conda-forge.
104
104
Usually, the bot will generate these migrations automatically. However, when a pin is first made or added, one may need to
105
105
be added by hand. To do this, follow these steps:
106
106
107
-
#. create a new migration yaml by copying `example.exyaml <https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/migrations/example.exyaml>`__ in the ``conda-forge/conda-forge-pinning`` repository.
108
-
#. change the migration yaml to reflect the package and version to be migrated
109
-
#. write a :ref:`migrator <pin_migrator>` for propagating the pin changes.
110
-
#. propose the changes as a :term:`PR` to `conda-forge/conda-forge-pinning-feedstock`_.
111
-
#. once accepted the migration will begin. The migration status can be monitored at https://conda-forge.org/status.
107
+
#. Create a new migration yaml by copying `example.exyaml <https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/migrations/example.exyaml>`__ in the ``conda-forge/conda-forge-pinning`` repository.
108
+
#. Change the migration yaml to reflect the package and version to be migrated
109
+
#. Write a :ref:`migrator <pin_migrator>` for propagating the pin changes.
110
+
#. Propose the changes as a :term:`PR` to `conda-forge/conda-forge-pinning-feedstock`_.
111
+
#. Once accepted the migration will begin. The migration status can be monitored at https://conda-forge.org/status.
112
112
#. After the migration is complete, a new PR can be issued to `conda-forge/conda-forge-pinning-feedstock`_ to:
113
113
114
114
- Remove the migrator yaml for the completed migration
115
115
- If the version of the package is pinned in the global conda_build_config.yaml, this PR should also:
116
116
117
-
- update the version in conda_build_config.yaml
118
-
- bump the version in meta.yaml to the current date
117
+
- Update the version in conda_build_config.yaml
118
+
- Bump the version in meta.yaml to the current date
119
119
120
120
Details of how the migration yaml is setup are provided in an `example <https://github.com/conda-forge/conda-forge-pinning-feedstock/tree/master/recipe/migrations/example.exyaml>`__
121
121
and documentation `here <https://regro.github.io/cf-scripts/migrators.html#building-a-migration-yaml>`_.
0 commit comments