Skip to content

test: add Expo compatibility CI job #1432

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

Draft
wants to merge 12 commits into
base: next
Choose a base branch
from

Conversation

grdsdev
Copy link
Contributor

@grdsdev grdsdev commented May 27, 2025

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

Copy link

snyk-io bot commented May 27, 2025

Snyk checks have failed. 1 issues have been found so far.

Icon Severity Issues
Critical 0
High 1
Medium 0
Low 0

code/snyk check is complete. 1 issues have been found. (View Details)

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.


const SUPABASE_URL = 'http://127.0.0.1:54321'
const ANON_KEY =
'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0'
Copy link

Choose a reason for hiding this comment

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

  Hardcoded Secret

Avoid hardcoding values that are meant to be secret. Found a hardcoded string used in here.

Line 7 | CWE-547 | Priority score 775
Data flow: 2 steps

Step 1 - 2

'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0'

@coveralls
Copy link

coveralls commented May 27, 2025

Pull Request Test Coverage Report for Build 15683177617

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 72.889%

Totals Coverage Status
Change from base Build 15611778513: 0.0%
Covered Lines: 109
Relevant Lines: 132

💛 - Coveralls

@grdsdev grdsdev force-pushed the guilherme/expo-compatibility-test branch 2 times, most recently from c4d6d35 to b17a9e2 Compare June 3, 2025 10:47
@grdsdev grdsdev force-pushed the guilherme/expo-compatibility-test branch 2 times, most recently from 764777a to b63febb Compare June 4, 2025 11:42
@grdsdev grdsdev force-pushed the guilherme/expo-compatibility-test branch from e0be4e2 to aea81b1 Compare June 12, 2025 13:25
grdsdev and others added 2 commits June 12, 2025 11:36
* fix: bump realtime-js

* fix: bump up realtime (#1443)

* fix: bump realtime-js (#1453)

* merge next into master (#1438)

* fix: bump realtime-js

* fix: bump up realtime (#1443)

---------

Co-authored-by: Filipe Cabaço <[email protected]>

* Next (#1444)

* fix: bump realtime-js

* fix: bump up realtime (#1443)

---------

Co-authored-by: Guilherme Souza <[email protected]>

* fix: bump up realtime (#1446)

* fix: bump realtime-js

* fix: bump up realtime

---------

Co-authored-by: Guilherme Souza <[email protected]>

* feat: bump auth-js to v2.70.0 (#1449)

* fix: update realtime-js

---------

Co-authored-by: Filipe Cabaço <[email protected]>
Co-authored-by: Stojan Dimitrovski <[email protected]>

* bump realtime-js

* fix: bump realtime-js (#1456)

* fix: bump realtime-js

* fix: bump realtime-js to 2.11.11-next.5

* test(deno): add integration tests for deno

* rollback running integration test twice

* downgrade deno

# Conflicts:
#	package-lock.json
#	pnpm-lock.yaml

* run only for deno 2

* add example deno

* move to test folder

* use old deno lock

* clean up

* ignore memory leak errors on test

* set broken supabase version for testing

* use latest supabase-js version

* regenerate deno.lock

* deno test using npm

* use clean-install

* remove lock file

* run build

* run tests only for deno 2

* run deno test twice

* run deno test twice

* chore: add imports section to `deno.json`

* chore: update `ci.yml`

* chore: create script for generating deno.json file

* remove deno.json

* run browser integration after node

* run setup-deps before running tests

* revert realtime-js version

* remove .tools-version

---------

Co-authored-by: Filipe Cabaço <[email protected]>
Co-authored-by: Stojan Dimitrovski <[email protected]>
Co-authored-by: Nyannyacha <[email protected]>
@grdsdev grdsdev force-pushed the guilherme/expo-compatibility-test branch from aea81b1 to 8354c3f Compare June 16, 2025 14:09
@grdsdev grdsdev force-pushed the guilherme/expo-compatibility-test branch from 8354c3f to d8e69f1 Compare June 16, 2025 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants