[IMPROVEMENT] skip (next) major version

Abierto
  • ¿Algo no está bien?
#5,657 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
cli, tooling

Línea de trabajo

The issue names no files, tests or entry points. Start by finding how UniGetUI already handles skipping or ignoring updates for a package, then check how version ranges are compared. Done would mean a design that lets a user keep receiving updates within their licensed major version while ignoring the next major, agreed with maintainers first.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement priority: medium
Please confirm these before moving forward.
  • I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
  • This improvement refers to an existing feature. If you want to suggest a new feature, please use this template.
  • This improvement is not a bug. If you want to report a bug, please use this template.
Describe the improvement

I have a few tools that are licensed. I have a license for upto a certain major version, but not the next major. Still for the version I have sometimes a new release is being made, and I would want to install that version.
UniGetUI allows to skip next versions, or to ignore updates as a whole.

The improvement feature I see is that I would be able to receive updates for my version, but ignore versions with a certain version pattern.

Describe how this improvement could help users

This new feature would help me, and others, accidentally updating to a new application version, then having to go through the pain of reverting.

Lenguaje dominante
C#
Estrellas
26.8k
Forks
970
Merge medio
17 h 24 min
PR fusionados (30 d)
126

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Devolutions/UniGetUI

Todos los issues de Devolutions/UniGetUI

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.