1. 11 7月, 2022 1 次提交
  2. 02 7月, 2022 1 次提交
    • J
      release: 4.5.0 (#5308) · 9ad0d9e6
      Joe Previte 提交于
      * chore(release): bump version to 4.5.0
      
      * chore: update CHANGELOG
      
      * chore: bump chart version
      
      * docs: update MAINTAINING
      
      * fix: add VSCODE_DEV=1 to e2e script
      
      I'm not sure what changed in the latest version but without setting
      VSCODE_DEV=1, code-server won't load. This fixes that.
      
      * Revert "fix: add VSCODE_DEV=1 to e2e script"
      
      This reverts commit 58c4826a.
      
      * fix: try setting VSCODE_DEV=1
      
      * Revert "fix: try setting VSCODE_DEV=1"
      
      This reverts commit 902f5f2f.
      
      * refactor: remove version check e2e test
      
      I am not sure why this is passing locally and failing CI. I need to
      further investigate this since it fails depending on where you test.
      9ad0d9e6
  3. 01 7月, 2022 1 次提交
  4. 30 6月, 2022 1 次提交
  5. 29 6月, 2022 3 次提交
  6. 25 6月, 2022 1 次提交
    • J
      refactor: move integration tests to Jest (#5275) · c51ff3bc
      Joe Previte 提交于
      * feat: add installExtension integration test
      
      This adds a new helper function called `runCodeServerCommand` along with
      a test for `--install-extension`. We can use this approach for writing
      integration tests (i.e. testing a real code-server build, CLI commands,
      etc).
      
      * refactor: s/ test:standalone with test:integration
      
      This replaces our integration approach to use Jest instead of a single
      bash script. By doing this, we will be able to easily maintain and add
      to our integration test suite.
      
      * refactor: filter unit tests
      
      Now that our integration tests also use Jest, we need to update our unit
      test script to ignore `test/integration`.
      
      * refactor: add SKIP_SUBMODULE_DEPS to postinstall
      
      * refactor: add SKIP_SUBMODULE_DEPS to postinstall
      
      * fixup!: skip submod deps
      
      * refactor: move runCodeServerCommand into sep. file
      
      When Jest runs a test, it loads all the files and imports for that test.
      This means you might be "requiring" code that's unrelated to your tests.
      
      This leads to unexpected errors depending on where the code runs.
      
      Moved this file to avoid GLIBC and other errors relaed to argon2 when
      running integration tests in CI.
      
      * fizup: formatting
      
      * fizup: increase timeout
      
      * refactor: use fixture in installExtension test
      
      Instead of relying on a network to install an extension, we use a
      fixture - vsix file in the repo. This is also faster.
      
      * feat: add integration test for listExtensions
      
      * chore: ignore integration fixtures
      
      * fixup: formatting
      
      * fixup: remove custom-hacks.css
      
      * fixup: formatting
      
      * Update test/integration/installExtension.test.ts
      Co-authored-by: NAsher <ash@coder.com>
      
      * Update test/integration/listExtensions.test.ts
      Co-authored-by: NAsher <ash@coder.com>
      
      * Update test/integration/installExtension.test.ts
      Co-authored-by: NAsher <ash@coder.com>
      
      * Update test/integration/listExtensions.test.ts
      Co-authored-by: NAsher <ash@coder.com>
      
      * fixup: contributing integration tests section
      
      * fixup: update ci/readme
      
      * fixup: use RELEASE_PATH in test-integration.sh
      
      * refactor: unzip vsix for listExtensions
      
      * refactor: use exec instead of spawn
      
      * Update docs/CONTRIBUTING.md
      Co-authored-by: NAsher <ash@coder.com>
      
      * Update test/integration/listExtensions.test.ts
      Co-authored-by: NAsher <ash@coder.com>
      
      * Update test/integration/listExtensions.test.ts
      Co-authored-by: NAsher <ash@coder.com>
      
      * Update test/integration/listExtensions.test.ts
      Co-authored-by: NAsher <ash@coder.com>
      
      * refactor: use different default binary path
      
      * fixup!: formatting
      Co-authored-by: NAsher <ash@coder.com>
      c51ff3bc
  7. 23 6月, 2022 2 次提交
  8. 22 6月, 2022 1 次提交
    • A
      chore: update Code to 1.68 (#5263) · 5ce99f8d
      Asher 提交于
      * chore: update Code to 1.67
      
      Was able to remove our changes to common/webview.ts since they are
      upstream now.
      
      Other than that no serious changes, just context diffs.
      
      * chore: update Code to 1.68
      
      - Upstream moved the web socket endpoint so change the Express route
        from / to *.  That will let web sockets work at any endpoint.
      - Everything in the workbench config is basically the same but
        de-indented (upstream extracted it into a separate object which
        resulted in a de-indent), the ordering is slightly different, and
        instead of vscodeBase we now need vscodeBase + this._staticRoute since
        everything is served from a sub-path now.
      - Move manifest link back to the root since that is where we host our
        manifest.
      - Change RemoteAuthoritiesImpl to use the same path building method as
        in other places (+ instead of using URI.parse/join).
      - Use existing host/port in RemoteAuthoritiesImpl and
        BrowserSocketFactory instead of patching them to use window.location
        (these are set from window.location to begin with so it should be the
        same result but with less patching).
      - Since BrowserSocketFactory includes a sub-path now (endpoints were
        changed upstream to serve from /quality/commit instead of from the
        root) the patch there has changed to prepend the base to that
        path (instead of using the base directly).
      - The workbench HTML now natively supports a base URL in the form of
        WORKBENCH_WEB_BASE_URL so no need for VS_BASE patches there anymore.
      - Upstream added type="image/x-icon" so I did as well.
      - Move the language patch to the end of the series so it is easier to
        eventually remove.
      - Remove the existing NLS config in favor of one that supports
        extensions.
      - Upstream deleted webview main.js and inlined it into the HTML so move
        that code (the parent origin check) into both those HTML files
        (index.html and index-no-csp.html).
      - The remaining diff is from changes to the surrounding context or a
        line was changed slightly by upstream (for example renamed files or
        new arguments like to the remote authority resolver).
      
      * fix: modify product.json before building
      
      Code injects this into the client during the build process so it needs
      to be updated before we build.
      
      * fix: update inline script nonces
      
      * Update HTML base path test
      
      * fix: missing commit
      
      Code overrides it with nothing.
      
      The date is also already injected.
      
      * fix: web extensions breaking when the commit changes
      
      By just using the marketplace directly instead of going through the
      backend.  I am not sure what the point is when searching extensions
      already goes directly to the marketplace anyway.
      
      But also remove the prefix that breaks this as well because otherwise
      existing installations will break.
      5ce99f8d
  9. 17 6月, 2022 1 次提交
  10. 16 6月, 2022 2 次提交
  11. 15 6月, 2022 1 次提交
  12. 14 6月, 2022 3 次提交
  13. 11 6月, 2022 1 次提交
  14. 07 6月, 2022 1 次提交
  15. 06 6月, 2022 1 次提交
  16. 21 5月, 2022 1 次提交
    • A
      fix: install nfpm straight from GitHub (#5214) · 5d47282e
      Asher 提交于
      * fix: install nfpm straight from GitHub
      
      install.goreleaser.com appears to no longer be available.
      
      * Add -f to curl commands
      
      This might have made it so we got the right error rather than erroring
      on the envsubst step.
      5d47282e
  17. 20 5月, 2022 1 次提交
  18. 14 5月, 2022 1 次提交
  19. 12 5月, 2022 2 次提交
  20. 11 5月, 2022 7 次提交
  21. 10 5月, 2022 2 次提交
  22. 07 5月, 2022 5 次提交