Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify bezier-vscode metadata for publish #2153

Merged

Conversation

yangwooseong
Copy link
Collaborator

@yangwooseong yangwooseong commented Apr 11, 2024

Self Checklist

  • I wrote a PR title in English and added an appropriate label to the PR.
  • I wrote the commit message in English and to follow the Conventional Commits specification.
  • I added the changeset about the changes that needed to be released. (or didn't have to)
  • I wrote or updated documentation related to the changes. (or didn't have to)
  • I wrote or updated tests related to the changes. (or didn't have to)
  • I tested the changes in various browsers. (or didn't have to)
    • Windows: Chrome, Edge, (Optional) Firefox
    • macOS: Chrome, Edge, Safari, (Optional) Firefox

Related Issue

Summary

  • extension 의 icon, publisherName, publisher 등 메타 데이터를 수정하고 배포합니다.

Details

  • 테스트 해봤을 때 scss, ts 파일에서 동작을 확인했습니다. 다만 tsx 파일에서는 동작하지 않네요. client.ts 에서 language: typescript, pattern: '**/*' 를 주고 테스트 했을 때도 안되서 이유는 나중에 찾아봐야할 것 같습니다.
  • 배포할 때는 bezier-vscode/ 밑에서 vsce package 명령어로 VSIX 파일을 만들고 수동으로 업로드했습니다.
  • 이전에 용량이 크다고 에러가 났던 것은 아마 extension 을 만들 때 상위 디렉토리까지 바라봐서 그런 것 같습니다. .vscodeignore 에 상위 디렉토리를 추가하니 번들러를 쓰지 않아도 해결되었습니다.
  • 배포된 링크: https://marketplace.visualstudio.com/items?itemName=ChannelCorp.bezier-vscode
  • extension 에 verified domain 로 https://channel.io 을 넣을 때 에러가 떠서 이슈에 문의중입니다. (#)

Breaking change? (Yes/No)

  • No

References

@yangwooseong yangwooseong added the bezier-vscode Issue or PR related to bezier-vscode label Apr 11, 2024
@yangwooseong yangwooseong self-assigned this Apr 11, 2024
Copy link

changeset-bot bot commented Apr 11, 2024

🦋 Changeset detected

Latest commit: deaa865

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
bezier-vscode Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

codecov bot commented Apr 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.63%. Comparing base (5fb439b) to head (56b3056).

❗ Current head 56b3056 differs from pull request most recent head deaa865. Consider uploading reports for the commit deaa865 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2153   +/-   ##
=======================================
  Coverage   86.62%   86.63%           
=======================================
  Files         126      126           
  Lines        2655     2656    +1     
  Branches      777      791   +14     
=======================================
+ Hits         2300     2301    +1     
  Misses        350      350           
  Partials        5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

"author": "Channel Corp.",
"publisher": "Channel Corp.",
"homepage": "https://github.com/channel-io/bezier-react/blob/main/packages/bezier-vscode/README.md",
"author": "Channel Corp",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • author 에는 . 를 넣을 수 없고 publisher 에는 alphanumeric 만 허용합니다.
  • vsce package 커맨드를 실행하면 vscode:prepublish 가 먼저 실행됩니다.

@yangwooseong yangwooseong changed the title Feat/modify vscode meta data Modify vscode metadata for publish Apr 11, 2024
@yangwooseong yangwooseong changed the title Modify vscode metadata for publish Modify bezier-vscode metadata for publish Apr 11, 2024
@channel-io channel-io deleted a comment from channeltalk-exp bot Apr 11, 2024
Copy link
Contributor

@sungik-choi sungik-choi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extension 에 verified domain 로 https://channel.io/ 을 넣을 때 에러가 떠서 이슈에 문의중입니다. (microsoft/vsmarketplace#795 (comment))

뒤에 /en path를 넣었을 때는 어떤가요? 리다이렉션 로직이 연관있을 거 같아서요

image

Copy link
Contributor

@sungik-choi sungik-choi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

배포할 때는 bezier-vscode/ 밑에서 vsce package 명령어로 VSIX 파일을 만들고 수동으로 업로드했습니다.

나중에 changeset이랑 묶어서 vscode 버저닝이 있다면 CI에서 vsce publish 실행시켜주는게 가장 좋을 거 같네요

"name": "@channel.io/bezier-vscode",
"version": "0.1.0",
"name": "bezier-vscode",
"version": "0.1.1",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

초기버전은 0.1.0 으로 배포했으면 좋았을 텐데 아쉽네요..! 패키지 이름이 바뀌어서 버전 롤백해도 괜찮았을 거 같아요

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extension 을 unpublish 하고 다시 만들어서 0.1.0 으로 맞추면 될 것 같습니다

Copy link
Collaborator Author

@yangwooseong yangwooseong Apr 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

그런데 다시 보니 bezier-vscode package 가 npm 배포가 안된 상태군요(#).. 혹시 왜 안되는지 아시나요? 다시 버전 0.0.0 으로 하고 changeset minor bump 해야할 것 같네요

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • package.json의 private 필드를 true로 둬서 그렇습니다. npm 레지스트리에 배포할 필요가 없는 패키지여서요..!
  • 말씀주신대로 하면 될 거 같습니다. CHANGELOG.md 파일도 제거하거나 해서 초기화해야할 거 같네요.

Copy link
Collaborator Author

@yangwooseong yangwooseong Apr 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

이 pr 이 머지되고 changeset pr 까지 머지되면 이번 pr 만 changelog 에 뜨게 되니 나중에 changelog 를 직접 수정을 해서 처음 pr(https://github.com/channel-io/bezier-react/pull/2091)을 추가해야할 것 같네요. extension 배포는 changeset pr까지 머지된 이후에 다시하겠습니다

@yangwooseong
Copy link
Collaborator Author

extension 에 verified domain 로 https://channel.io/ 을 넣을 때 에러가 떠서 이슈에 문의중입니다. (microsoft/vsmarketplace#795 (comment))

뒤에 /en path를 넣었을 때는 어떤가요? 리다이렉션 로직이 연관있을 거 같아서요

image

테스트해봤을 때 안되었습니다

image

@sungik-choi
Copy link
Contributor

Eligible domains
Eligible domains meet the following criteria:

  • You must be able to manage the DNS configuration settings and add a TXT record.
  • It is not a subdomain ({subdomain}.github.io, {subdomain}.contoso.com, or similar).
  • It must use an HTTPS protocol.
  • It must be able to respond with an HTTP 200 status to a HEAD request.

라고 하네요. 홈페이지에서 200을 내려주도록 해야할 듯..?

@yangwooseong
Copy link
Collaborator Author

Eligible domains
Eligible domains meet the following criteria:

  • You must be able to manage the DNS configuration settings and add a TXT record.
  • It is not a subdomain ({subdomain}.github.io, {subdomain}.contoso.com, or similar).
  • It must use an HTTPS protocol.
  • It must be able to respond with an HTTP 200 status to a HEAD request.

라고 하네요. 홈페이지에서 200을 내려주도록 해야할 듯..?

클라이언트 위치에 따라서 리다이렉션을 거는 것으로 알고있어서 이것을 없앨 수 있을지 모르겠네요. 한 번 여쭤볼게요

"bezier-vscode": minor
---

Modify `bezier-vscode` package.json for displayName and icon
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

초기 릴리즈라는 정보가 담기도록 변경되면 좋을 거 같아요. 어차피 첫번째 버전으로 퍼블리시될거라 무엇이 변경되었다가 changelog에선 큰 의미가 없을 거 같아요.

@yangwooseong yangwooseong force-pushed the feat/modify-vscode-meta-data branch from 0b68cb9 to 588800f Compare April 12, 2024 02:52
github-actions bot and others added 9 commits April 12, 2024 11:53
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

- Fixes an issue where injecting `className` into `FormLabel`,
`FormHelperText` inside a `FormControl` does not apply styles correctly.
([channel-io#2156](channel-io#2156)) by
@sungik-choi

-   Updated dependencies
    -   @channel.io/[email protected]

- Add "color" prefix to alpha color tokens and fix misnaming of alpha
font/typography tokens.
([channel-io#2152](channel-io#2152)) by
@sungik-choi

-   Updated dependencies
    -   @channel.io/[email protected]

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
- add icon
- modify publisher and author name valid
- `vsce package` command will include parent directory and throw error because of massive volume
@yangwooseong yangwooseong force-pushed the feat/modify-vscode-meta-data branch from 588800f to deaa865 Compare April 12, 2024 02:53
@yangwooseong yangwooseong merged commit aed8dbd into channel-io:main Apr 12, 2024
7 checks passed
@yangwooseong yangwooseong deleted the feat/modify-vscode-meta-data branch April 12, 2024 02:56
yangwooseong pushed a commit that referenced this pull request Apr 12, 2024
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## [email protected]

### Minor Changes

- Set up information about the package for initial publishing
([#2153](#2153)) by
@yangwooseong

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
yangwooseong added a commit that referenced this pull request Apr 12, 2024
<!--
  How to write a good PR title:
- Follow [the Conventional Commits
specification](https://www.conventionalcommits.org/en/v1.0.0/).
  - Give as much context as necessary and as little as possible
  - Prefix it with [WIP] while it’s a work in progress
-->

## Self Checklist

- [x] I wrote a PR title in **English** and added an appropriate
**label** to the PR.
- [x] I wrote the commit message in **English** and to follow [**the
Conventional Commits
specification**](https://www.conventionalcommits.org/en/v1.0.0/).
- [x] I [added the
**changeset**](https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md)
about the changes that needed to be released. (or didn't have to)
- [x] I wrote or updated **documentation** related to the changes. (or
didn't have to)
- [x] I wrote or updated **tests** related to the changes. (or didn't
have to)
- [x] I tested the changes in various browsers. (or didn't have to)
  - Windows: Chrome, Edge, (Optional) Firefox
  - macOS: Chrome, Edge, Safari, (Optional) Firefox

## Related Issue

<!-- Please link to issue if one exists -->

<!-- Fixes #0000 -->

- None

## Summary

<!-- Please brief explanation of the changes made -->

- #2153 에서 버전이 롤백되었기 때문에 #2091 이 changelog 에 들어가있지 않습니다. 이것을 직접 추가합니다. 

## Details

<!-- Please elaborate description of the changes -->

- 생략

### Breaking change? (Yes/No)

<!-- If Yes, please describe the impact and migration path for users -->

- No

## References

<!-- Please list any other resources or points the reviewer should be
aware of -->

-
#2153 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bezier-vscode Issue or PR related to bezier-vscode
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants