chore: add @legacy to install script #2058
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### [커밋 타입]: [작업내용] ##### 본문 - 한 줄에 최대 72 글자까지만 입력하기 # 1. 무엇을 수정했는지 # 2. 왜 수정했는지 # 꼬릿말은 아래에 작성: ex) #이슈 번호 - # [커밋 타입] 리스트 # feat : 기능 (새로운 기능) # fix : 버그 (버그 수정) # refactor : 리팩토링 # style : 스타일 (코드 형식, 세미콜론 추가: 비즈니스 로직에 변경 없음) # docs : 문서 (문서 추가, 수정, 삭제) # test : 테스트 (테스트 코드 추가, 수정, 삭제: 비즈니스 로직에 변경 없음) # chore : 기타 변경사항 (빌드 스크립트 수정 등) # post : 블로그 포스트 추가 (신규 포스트 작성 및 수정) # ------------------ # [체크리스트] # 제목 첫 글자는 대문자로 작성했나요? # 제목은 명령문으로 작성했나요? # 제목 끝에 마침표(.) 금지 # 제목과 본문을 한 줄 띄워 분리하기 # 본문에 여러줄의 메시지를 작성할 땐 "-"로 구분했나요? # ------------------ Now, when the script is executed the latest version is installed. I think we need to add "@legacy" to install version 1.3.4
✅ Deploy Preview for vue-test-utils-v1 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now, when the script is executed the latest version is installed. I think we need to add "@legacy" to install version 1.3.4
What kind of change does this PR introduce? (check at least one)
Editing docs.
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch.fix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: